Tool reference
The tools Infra's MCP server offers, by toolset, with what each is for.
This page lists the tools by toolset. Your connection shows only the tools your role, your pages and your credential allow, from the toolsets in its URL. Call edge_whoami to see your own list. See Connecting agents for how toolsets are turned on.
Tool names start with edge_ (Infra and Delivery), dle_ (Sales, the Deal Lifecycle Engine) or kb_ (the knowledge base).
core (on by default)
Who you are and engagements
| Tool | What it does |
|---|---|
edge_whoami | Your identity, role, departments, scopes, whether you can write, and your tools. Call it first. Always listed. |
edge_list_engagements | The engagements you can reach, with their projects. |
edge_get_engagement_context | One engagement whole: its projects, team, knowledge documents with their text, requirements and document list. Very long bodies are withheld; fetch them with edge_get_document. |
edge_get_document | One knowledge document in full. Pass layer to get original, transcript, summary or all. |
Project reads
| Tool | What it does |
|---|---|
edge_get_delivery_plan | The project's approved plan: SOWs, requirements, deliverables, milestones, decisions, test cases, agreements, RAID, gaps and amendments, with every item's id. |
edge_get_item | One project item by its code (for example REQ-012) or id, with its history. |
edge_get_system_build | The project's system build: plans, components, interfaces, build objects. |
edge_project_timeline | The project's dates and milestone forecasts. |
edge_project_trace | Why an item exists, with its source passage. |
edge_list_changes | Proposed changes, with their citations. |
edge_list_queue | The Events review queue, grouped by source document. |
edge_get_sync_status | Documents Sync has not read yet. Free. |
Everyday deals
| Tool | What it does |
|---|---|
dle_get_dashboard | DLE totals. |
dle_list_deals, dle_get_deal | Deals, and one deal with sections such as rubric, readiness and stage history. |
dle_list_deal_activity | A deal's activity feed. |
dle_create_deal, dle_update_deal | Create or edit a deal. |
dle_advance_deal, dle_regress_deal | Move a deal to the next stage (may be held by its gates) or back, with a reason. |
dle_add_stage_note | Add a note against a stage. Append-only. |
dle_run_readiness_check | Score the deal's stage rubric: ADVANCE or HOLD. |
dle_list_leads, dle_get_lead, dle_list_contacts | Leads and contacts. |
kb (on by default)
| Tool | What it does |
|---|---|
kb_search | Ranked passages from the company wiki. |
kb_document | One wiki page in full, by its path. |
kb_tree | The tree of wiki pages you can reach. |
rag_search | Search the indexed knowledge base, with content inline. |
edge_search | Older name for knowledge search. Prefer kb_search. |
dle
The full deal lifecycle: methodology and stage rubric reads (dle_get_methodology, dle_get_stage_rubric), rubric items (dle_update_rubric_item), custom fields, pausing, AI readiness enrichment (start and poll), the catch-up protocol for vendor-sourced deals, vendor risk, mutual action plans and their milestones, margin approval and override requests, ceilings, pending overrides, vendor partners, leads and contacts (create, update, convert a lead to a deal), and assignable users.
dle-destructive
Each needs a confirmed second call.
| Tool | What it does |
|---|---|
dle_close_deal | Close a deal as won, or lost with a loss reason. |
dle_disqualify_deal | Disqualify a deal. |
dle_record_readiness_decision | Record ADVANCED, HELD or OVERRIDDEN on a readiness report. |
dle_approve_margin, dle_reject_margin | Decide a margin approval. |
dle_review_override | Decide an override request. |
dle_delete_map_milestone | Delete a mutual action plan milestone. |
dle-admin
Admins only. Methodology, stages, stage rubrics and thresholds, loss reasons and their categories, the catch-up protocol, vendor partners, custom field groups, definitions and options, ceiling evaluation, and bulk deal import (template, preview, confirm). Creating a methodology with stages activates it and deactivates the current one, org-wide, so it needs confirmation.
delivery
| Tool | What it does |
|---|---|
edge_project_search | Find a project's documents and items. A code (DEC-015), a person's name or a platform object name goes straight to its record; words search titles and text. |
edge_add_project_document | Add a Markdown or text document to a project's Knowledge, with its transcript and a digest. See Staging documents with a digest. |
edge_sync_project | Read new or changed documents into proposed changes. Uses AI per document. When it answers with remaining above 0, call it again. |
edge_stage_change | Propose up to 50 changes for the lead, each citing its source. |
edge_update_queued_change | Fix a change waiting in the queue before review. |
edge_review_queue | Approve or dismiss queue rows. Project lead or admin only, up to 25 rows per call. |
edge_add_project_sow | Record a SOW version as draft or pending. Only a person signs a SOW. |
edge_update_project | Edit a project's lead and dates. |
edge_update_engagement | Edit an engagement's key facts. Engagement owners and admins only. |
What agents cannot do on purpose
- Sign a SOW or BRD, or attach their documents. A person does that in Infra.
- Edit approved project state directly. Agents stage a change instead.
- Pin a milestone forecast or answer a question so that it applies at once. A key's answer always waits for review.
Results and errors
A refusal comes back in one of two ways:
- Before any tool runs, as an HTTP error: no or bad credential (401), a credential without the needed scope (403), too many calls (429).
- Inside a tool call, as a tool result with a
code:invalid_argument,forbidden,not_found_or_out_of_scope(a record you cannot see reads the same as one that does not exist),conflictand others.
Some results are business outcomes, not errors: gate_held (a deal's gates held it; the result says what is missing) and confirmation_required (call again with the token).