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

agent-passport-system-mcp

by agent-passport-system
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Check Tier Permits Action

check_tier
Read-onlyIdempotent

Verifies whether an agent's earned tier permits a requested action at a given autonomy level and spend amount, returning null if allowed or escalation details if not.

Instructions

Check if an agent's earned tier permits an action at a given autonomy level and spend amount. Returns null if permitted, or escalation details if tier is insufficient.

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": {
      "agentId": "<agentId>",
      "principalId": "<principalId>",
      "scope": "<scope>"
    },
    "name": "check_tier"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeYesReputation scope
agentIdYesAgent ID
principalIdYesPrincipal ID
requestedDepthNoRequested delegation depth
requestedSpendNoRequested spend amount in dollars
requestedAutonomyNoRequested autonomy level (1-5)

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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, and the description adds genuinely useful return semantics beyond them: 'Returns null if permitted, or escalation details if tier is insufficient.' This is valuable given there is no output schema, though it stops short of describing what the escalation details contain or any failure modes.

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

Conciseness5/5

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

Two sentences with zero waste. The core purpose is front-loaded and the return behavior follows immediately, both earning their place.

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

Completeness4/5

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

For a read-only check tool with no output schema, the description covers the essential outcome (null vs. escalation details). It is largely complete, though the shape of the 'escalation details' return remains unspecified.

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 the schema fully documents all six parameters and the baseline is 3. The description references autonomy level and spend amount, mapping loosely to requestedAutonomy and requestedSpend, but adds no format or range detail beyond the schema.

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?

The description states a specific verb (Check) and resource (agent's earned tier permitting an action), qualified by autonomy level and spend amount. This distinguishes it functionally from sibling checks like check_purpose_permitted or check_usage_permitted, though it doesn't name any sibling explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the purpose ('at a given autonomy level and spend amount') but there is no explicit when-to-use guidance, no prerequisites, and no routing to alternatives such as aps_check_escalation_required or the other check_* tools.

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