Skip to main content
Glama

The Local Upgrade — Software Engineering

Ask an engineering or partnership question

request_email_followup
Idempotent

Saves a business inquiry and authorized reply contact. Use for procurement, delivery partnerships, confidential engagement setup or questions before a full brief. No newsletter signup.

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": {
      "requestId": "<requestId>",
      "question": "<question>",
      "contact": "<contact>",
      "agent": "<agent>",
      "consent": "<consent>"
    },
    "name": "request_email_followup"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYes
consentYes
contactYes
questionYes
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the write-but-safe, outward-facing profile is covered. The description adds that a reply contact is being captured and that it must be authorized, which is useful, but says nothing about what happens after submission — response channel, latency, or what requestId does. Marginal value beyond 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?

Two tight sentences with the core action front-loaded and the use-case list compressed into one clause. "No newsletter signup" is a slightly odd trailing exclusion but it is short and does real routing work.

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?

For a five-parameter, all-required, nested-object write tool with no output schema and zero schema descriptions, the definition is thin. It omits idempotency semantics, the consent/authorization requirement, and any hint of what the caller gets back, leaving the agent to infer behaviour from the schema's const constraints.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five required parameters including two nested objects, so the description carries the full burden and mostly fails. It hints at the question ("business inquiry") and contact ("authorized reply contact"), but never explains requestId as an idempotency key, the agent object's authorizedByRequester flag, or that consent is a required const-true acknowledgement.

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?

Uses a specific verb+resource: "Saves a business inquiry and authorized reply contact." That is clear enough to separate it from read-only siblings like get_procurement_information or review_engineering_evidence, though it never names a sibling. The title ("Ask an engineering or partnership question") adds a second framing that the description only partially reconciles.

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

Usage Guidelines4/5

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

Gives concrete when-to-use triggers — procurement, delivery partnerships, confidential engagement setup, questions before a full brief — and one explicit exclusion, "No newsletter signup." It doesn't say when to prefer request_proposal or prepare_engagement_brief instead, so the routing to siblings is implied rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources