Skip to main content
Glama

verify_stamp

Verify AgentStamp identity certificates using stamp IDs to confirm agent authenticity and trustworthiness.

Instructions

Verify an AgentStamp identity certificate by its stamp ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stamp_idYesThe stamp ID to verify (e.g., stmp_QLNhL-Y1CvlyWxnG)

Implementation Reference

  • The implementation of the 'verify_stamp' tool handler, including input validation and certificate verification logic.
    server.tool(
      'verify_stamp',
      'Verify an AgentStamp identity certificate by its stamp ID.',
      {
        stamp_id: z.string().describe('The stamp ID to verify (e.g., stmp_QLNhL-Y1CvlyWxnG)'),
      },
      async ({ stamp_id }) => {
        const { getDb } = require('./database');
        const { verifyCertificate, getPublicKey } = require('./crypto');
        const db = getDb();
    
        const stamp = db.prepare('SELECT * FROM stamps WHERE id = ?').get(stamp_id);
        if (!stamp) {
          return { content: [{ type: 'text', text: JSON.stringify({ error: 'Stamp not found' }) }] };
        }
    
        const certificate = JSON.parse(stamp.certificate);
        const isValid = verifyCertificate(certificate, stamp.signature);
        const isExpired = new Date(stamp.expires_at) < new Date();
    
        return {
          content: [{
            type: 'text',
            text: JSON.stringify({
              stamp_id: stamp.id,
              tier: stamp.tier,
              wallet_address: stamp.wallet_address,
              issued_at: stamp.issued_at,
              expires_at: stamp.expires_at,
              valid: isValid && !isExpired && !stamp.revoked,
              expired: isExpired,
              revoked: !!stamp.revoked,
              signature_valid: isValid,
              public_key: getPublicKey(),
            }, null, 2),
          }],
        };
      }
    );
Behavior2/5

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

No annotations provided, so description carries full behavioral disclosure burden. 'Verify' implies a read-only validity check but doesn't specify what verification entails (cryptographic check? revocation check?), output format, or whether the operation is idempotent.

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?

Single sentence, front-loaded with action verb, zero redundancy. Appropriate length for a simple single-parameter tool.

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?

Adequate for a simple 1-parameter tool with complete schema documentation, though lacks output description (what does verification return? boolean? certificate data?). Given lack of output schema, description should ideally indicate expected return behavior.

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 coverage is 100% with detailed parameter description and example. Tool description adds domain context ('AgentStamp identity certificate') clarifying what the stamp_id represents, but doesn't add syntax constraints or usage patterns beyond schema documentation.

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?

Clear verb ('Verify') and resource ('AgentStamp identity certificate') with identifier specified. Mentions 'AgentStamp' which distinguishes from generic 'get_verifiable_credential' sibling, though could better explain the specific identity verification scenario vs other trust-checking tools.

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?

Contains no guidance on when to use this tool versus alternatives like 'get_verifiable_credential', 'get_passport', or 'trust_check'. No mention of prerequisites or failure conditions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vinaybhosle/agentstamp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server