Skip to main content
Glama

Send a request to Anchor Terminal

contact

Send a message to the Anchor Terminal team (a tool to add, a claim, a correction, an enquiry), answered by a person by email. Use it only when your user asks you to get in touch.

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": {
      "kind": "<kind>",
      "email": "<email>"
    },
    "name": "contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA domain, repository, endpoint or evidence link
kindYeslisting (a tool to add, by url), claim, dispute, general, enterprise, partner, compliance, audit or waitlist
nameNoWho's asking
emailYesWhere the reply goes, an address your user reads
dryRunNotrue: changes nothing
companyNoThe company it's for
listingNoThe listing it's about: a slug from search_tools, e.g. exa-mcp
messageNoThe request; optional only for waitlist. For an audit, the tools in scope, one per line
productNowaitlist only: letme (calling through letme), the default

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / dryRun
      Added value: +{
      +  "description": "true: changes nothing",
      +  "type": "boolean"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"audit: an agent-readiness audit of a company's tools; listing: a tool to add to the directory, named by url; claim or dispute: a listing; enterprise or partner: an enquiry; compliance: the tools a company's agents use, to research first; general: anything else; waitlist: a place on a waitlist (product); dataset: the research dataset, which is taken from the site's own form at /academia/ by someone signed in with a university address or a journalist's at their publication, not over MCP"New value: +"listing (a tool to add, by url), claim, dispute, general, enterprise, partner, compliance, audit or waitlist"
    • changedInput schema / properties / message / description
      Previous value: -"The request, required except for waitlist (where it's an optional note of at most 500 characters). For an audit, the tools in scope (URLs, package names or MCP endpoints), one per line, saying which are internal"New value: +"The request; optional only for waitlist. For an audit, the tools in scope, one per line"
  3. Changed1 schema field changed
    • changedInput schema / properties / kind / description
      Previous value: -"audit: an agent-readiness audit of a company's tools; listing: a tool to add to the directory, named by url; claim or dispute: a listing; enterprise or partner: an enquiry; compliance: the tools a company's agents use, to research first; general: anything else; waitlist: a place on a waitlist (product); dataset: the research dataset, which is taken from the site's own form at /academia/ by someone signed in with a university address, not over MCP"New value: +"audit: an agent-readiness audit of a company's tools; listing: a tool to add to the directory, named by url; claim or dispute: a listing; enterprise or partner: an enquiry; compliance: the tools a company's agents use, to research first; general: anything else; waitlist: a place on a waitlist (product); dataset: the research dataset, which is taken from the site's own form at /academia/ by someone signed in with a university address or a journalist's at their publication, not over MCP"
  4. Changed2 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"audit: an agent-readiness audit of a company's tools; listing: a tool to add to the directory, named by url; claim or dispute: a listing; enterprise or partner: an enquiry; compliance: the tools a company's agents use, to research first; general: anything else; waitlist: a place on a waitlist (product)"New value: +"audit: an agent-readiness audit of a company's tools; listing: a tool to add to the directory, named by url; claim or dispute: a listing; enterprise or partner: an enquiry; compliance: the tools a company's agents use, to research first; general: anything else; waitlist: a place on a waitlist (product); dataset: the research dataset, which is taken from the site's own form at /academia/ by someone signed in with a university address, not over MCP"
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "audit",
      -  "listing",
      -  "claim",
      -  "dispute",
      -  "enterprise",
      -  "partner",
      -  "compliance",
      -  "general",
      -  "waitlist"
      -]New value: +[
      +  "audit",
      +  "listing",
      +  "claim",
      +  "dispute",
      +  "enterprise",
      +  "partner",
      +  "compliance",
      +  "general",
      +  "waitlist",
      +  "dataset"
      +]
  5. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent call, so the safety baseline is covered. The description adds that a human replies by email — implying latency and a real outward-facing message — but says nothing about whether the submission can be retracted, what confirmation comes back, or how dryRun behaves (only the schema hints at that).

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, zero filler, and the core action plus the usage constraint are both front-loaded. A conditional reader can stop after sentence one if they only need to know what it does.

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?

There is no output schema, yet the description never says what the caller gets back on success — an acknowledgement, a reference id, or nothing. For a nine-parameter outward-facing submission tool that gap matters, though the 100% schema coverage and annotations carry most of the remaining load.

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 already defines all nine parameters including the kind and product enums. The description's parenthetical ("a tool to add, a claim, a correction, an enquiry") loosely maps to several kind values but adds no constraints or format guidance 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?

States a specific verb and resource ("Send a message to the Anchor Terminal team") plus the channel and handler ("answered by a person by email"), and parenthesizes the kinds of requests it carries. It does not differentiate itself from similar siblings such as file_issue, so it stops short of a 5.

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 an explicit gating condition: "Use it only when your user asks you to get in touch," which tells the agent not to fire it proactively. No alternative tool is named for cases where the user has not asked, so there is an implicit decision left to the agent.

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