agent-passport-system-mcp

Assign Agent to Task Role

assign_agent

Assign an agent to a task role and automatically create a scoped delegation with spend limits and Ed25519 public key verification.

Instructions

[OPERATOR] Assign an agent to a role in a task. Creates a delegation automatically.

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>",
      "role": "<role>",
      "agent_id": "<agent_id>",
      "agent_public_key": "<agent_public_key>",
      "scope": "<scope>"
    },
    "name": "assign_agent"
  }
}

Input Schema

Name	Required	Description
`role`	Yes	Role to assign
`scope`	Yes	Delegation scopes
`task_id`	Yes	Task ID
`agent_id`	Yes	Agent ID
`spend_limit`	No	Max spend
`agent_public_key`	Yes	Agent's Ed25519 public key

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv4.0.0Aug 1, 2026

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
```

Addedv2.8.0May 1, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations declare write/non-idempotent/non-destructive, so the safety profile is already covered. The description adds two genuinely useful traits beyond that: the [OPERATOR] tag signals an elevated authorization requirement, and 'Creates a delegation automatically' discloses a non-obvious side effect that a caller would otherwise not anticipate from the name.

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?

Two compact sentences with the authorization marker and the core action front-loaded. No filler, though the bracketed prefix is slightly cryptic without explanation.

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

Completeness3/5

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

For a 6-parameter mutation with no output schema, the description covers purpose and the auto-delegation side effect but omits what the tool returns, whether spend_limit caps are enforced, and the exact privilege implied by [OPERATOR]. Adequate but leaves real gaps an agent must infer.

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%, so all six parameters (task_id, role, agent_id, agent_public_key, scope, spend_limit) are documented in the schema. The description adds no syntax, format, or default detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb+resource ('assign an agent to a role in a task') and adds the automatic-delegation side effect. It is distinguishable from siblings like create_delegation because it frames delegation as a consequence of role assignment rather than the primary action, though it does not explicitly say when to prefer this over create_delegation.

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?

No when-to-use, prerequisites, or alternative guidance. The [OPERATOR] prefix hints at a privilege requirement but the description never states the condition that selects this tool versus create_delegation, create_v2_delegation, or accept_assignment.

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

Deploy Server