Skip to main content
Glama
Sign In
agent-passport-system-mcp

agent-passport-system-mcp

by agent-passport-system
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Submit Deliverable

submit_deliverable

Submit final task output with linked evidence packets, citations, and flagged gaps so reviewers can verify it against the required spec.

Instructions

[ANALYST/BUILDER] Submit your final output tied to evidence.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "task_id": "<task_id>",
      "spec_id": "<spec_id>",
      "content": "<content>",
      "evidence_packet_ids": "<evidence_packet_ids>",
      "citation_count": "<citation_count>",
      "gaps_flagged": "<gaps_flagged>"
    },
    "name": "submit_deliverable"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesThe deliverable content
spec_idYesDeliverable spec ID from the brief
task_idYesTask ID
gaps_flaggedYesNumber of gaps explicitly flagged
citation_countYesNumber of citations in output
evidence_packet_idsYesEvidence packet IDs used

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv2.8.0

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare the write profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), so the description only needs to add context such as whether a resubmission overwrites, duplicates, or is rejected after review. It adds none of this, and nothing about validation failures or downstream review.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with a role tag and no filler. It is efficient, though the extreme brevity for a six-required-parameter submission tool borders on under-specification rather than true conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with six required parameters, no output schema, and terminal-sounding semantics, the description never says whether submission is final, what happens after (review/acceptance), or how the citation and gap counts are validated. Annotations cover the safety profile, but the operational picture remains incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% across six required parameters, so the baseline is 3. The phrase 'tied to evidence' loosely signals that evidence_packet_ids must reference real packets, but citation_count and gaps_flagged — self-reported quality metrics — get no interpretive guidance in either field.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb (Submit) and resource (final output/deliverable) and tags the acting roles as [ANALYST/BUILDER], which helps an agent self-select. It does not, however, distinguish itself from closely related siblings such as submit_evidence or complete_task, which also move work product along.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The [ANALYST/BUILDER] tag implies who may call it, but there is no statement of when to submit versus using complete_task, submit_evidence, or handoff_evidence, and no prerequisites or ordering constraints (e.g., that a task brief/spec must exist first).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools