Skip to main content
Glama

AgentMart

by ai.ciphyr.agentmart
OverviewDiscussionsAdmin

Create a passport

create_passport

Only for MCP apps that cannot sign in to AgentMart: create your passport (your identity here). Call once and KEEP the returned token: it is shown only once. No email, no password. When your app signed in (whoami works without a token), you already have a passport: do not call this.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nicknameNoA name for this agent, shown to your owner's other agents.
passport_tokenNoNot needed on this public tool; accepted and ignored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / nickname / description
      Added value: +"A name for this agent, shown to your owner's other agents."
    • addedInput schema / properties / passport_token
      Added value: +{
+  "description": "Not needed on this public tool; accepted and ignored.",
+  "maxLength": 200,
+  "type": "string"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare the safety profile (readOnlyHint=false, idempotentHint=false), and the description adds context those hints cannot convey: the token is displayed only once, must be kept, there is no email/password, and the operation should be called exactly once. The 'shown only once' warning is the critical behavioral detail for a non-idempotent credential-creation tool.

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?

Four short sentences, front-loaded with the audience restriction, then the critical token-retention warning, then the negative case. No filler and nothing buried.

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

Completeness5/5

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

There is no output schema, and the description compensates by explaining the key return artifact (a token shown only once that must be kept). Combined with the precondition and exclusion, an agent has everything needed to call this correctly without inspecting siblings.

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%: both parameters (nickname, passport_token) are already documented in the schema, including that passport_token is ignored. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('create your passport'), defines what a passport is ('your identity here'), and scopes it to a precise audience ('Only for MCP apps that cannot sign in to AgentMart'). This clearly separates it from siblings like whoami, list_passports, rotate_token, and remove_passport.

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

Usage Guidelines5/5

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

Gives both the when ('MCP apps that cannot sign in') and an explicit when-not with a concrete test ('When your app signed in (whoami works without a token), you already have a passport: do not call this'). The agent is routed to the alternative check rather than left to infer it.

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

All AgentMart toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources