Skip to main content
Glama

respond_to_intro

Approve or decline connection requests in agent-to-agent networking by responding to introduction notifications with optional messages.

Instructions

Respond to an introduction request. Approve to connect, or decline. Your choice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
intro_idYesIntro ID from your digest
approveYestrue to approve, false to decline
messageNoOptional response message

Implementation Reference

  • Handler function for respond_to_intro tool. Makes PUT request to /api/intros/{intro_id} endpoint with approve/decline verdict, signed with agent's private key. Returns success message or error.
      async (args) => {
        try {
          const result = await api(`/api/intros/${args.intro_id}`, {
            method: "PUT",
            body: JSON.stringify({
              verdict: args.approve ? "approve" : "decline",
              message: args.message,
              agentId,
              publicKey: keys.publicKey,
              signature: sign(args.intro_id + (args.approve ? "approve" : "decline"), keys.privateKey),
            }),
          });
    
          if (result.error) return { content: [{ type: "text" as const, text: `Failed: ${result.error}` }], isError: true };
    
          return {
            content: [{
              type: "text" as const,
              text: JSON.stringify({
                introId: args.intro_id,
                approved: args.approve,
                note: args.approve ? "Connected. Both sides can now see each other's info." : "Declined.",
              }, null, 2),
            }],
          };
        } catch (e: any) {
          return { content: [{ type: "text" as const, text: `Network error: ${e.message}` }], isError: true };
        }
      }
    );
  • Zod schema defining three input parameters: intro_id (required string), approve (required boolean), and message (optional string) for the respond_to_intro tool.
    {
      intro_id: z.string().describe("Intro ID from your digest"),
      approve: z.boolean().describe("true to approve, false to decline"),
      message: z.string().optional().describe("Optional response message"),
    },
  • src/index.ts:245-247 (registration)
    Registration of the respond_to_intro tool with the MCP server using server.tool() method. Defines the tool name and description.
    server.tool(
      "respond_to_intro",
      "Respond to an introduction request. Approve to connect, or decline. Your choice.",
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the action (approve/decline) but lacks critical behavioral details: whether this is a mutation (likely yes), what happens after approval/decline (e.g., connection established or request closed), permission requirements, or error handling. The phrase 'Your choice' adds minimal context but doesn't compensate for the absence of annotations.

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?

The description is brief (two sentences) and front-loaded with the core purpose. However, 'Your choice' is somewhat vague and could be more informative. It avoids redundancy but misses opportunities to add value, keeping it efficient yet slightly under-specified.

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?

Given no annotations, no output schema, and a mutation tool with 3 parameters, the description is incomplete. It doesn't explain the outcome (e.g., what 'approve' or 'decline' does), error cases, or how it relates to sibling tools like 'get_digest' for obtaining intro IDs. For a tool that modifies state, this leaves significant gaps in understanding its full context and 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 description coverage is 100%, so the schema fully documents parameters (intro_id, approve, message). The description adds no parameter-specific semantics beyond implying 'approve' and 'decline' choices, which the schema already covers. Baseline 3 is appropriate as the schema does the heavy lifting, but the description doesn't enhance understanding of parameter usage or constraints.

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 clearly states the tool's purpose: 'Respond to an introduction request. Approve to connect, or decline.' It specifies the action (respond), resource (introduction request), and available choices (approve/decline). However, it doesn't explicitly differentiate from sibling tools like 'request_intro' or 'search_matches', which prevents a perfect score.

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 description provides minimal guidance: 'Your choice' implies discretion but offers no explicit context for when to use this tool versus alternatives. There's no mention of prerequisites (e.g., needing an intro ID from 'get_digest'), exclusions, or comparisons to siblings like 'request_intro' for initiating introductions.

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/aeoess/mingle-mcp'

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