Skip to main content
Glama

Contact Signa

contact_signa

Email the Signa team a request on behalf of the person you work for. A person reads it and replies to the email address given. Describe the business and the work they want help with.

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": {
      "name": "<name>",
      "email": "<email>",
      "message": "<message>"
    },
    "name": "contact_signa"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull name of the person Signa should reply to.
agentNoOptional name of the agent or app sending this.
emailYesTheir email address. Signa replies here.
companyNoCompany name, if any.
messageYesWhat they are looking for: the business, the work that piles up, and what better looks like.
websiteNoCompany website, if any.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a non-read-only, open-world, non-idempotent call, so the safety profile is known. The description adds context annotations cannot carry: a human reads the submission and replies out-of-band to the supplied email address, meaning there is no immediate tool result and the outcome arrives asynchronously. It stops short of stating response time, rate limits, or what happens if the email is invalid.

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?

Three short sentences, front-loaded with the action, then the human-reply mechanic, then the content expectation. Nothing is wasted, though the third sentence overlaps noticeably with the 'message' field description in the schema.

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

Completeness4/5

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

With no output schema, the description correctly supplies the missing return channel — the reply arrives by email rather than in the tool result, which is the key thing an agent must know before calling. Combined with fully documented parameters, the only residual gap is timing and failure behavior.

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

Parameters4/5

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

Schema coverage is 100%, so all six fields are already documented and the baseline is 3. The description earns above baseline by fixing the frame — 'on behalf of the person you work for' clarifies that name/email belong to the human principal rather than the agent, which matters because an optional 'agent' field also exists and could be confused for the sender identity.

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 — 'Email the Signa team a request' — plus the actor on whose behalf it is sent. The purpose is unambiguous, though it never names the sibling about_signa to contrast informational lookups with actually contacting the team.

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

Usage Guidelines3/5

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

Usage is implied: reach for this when the user wants to contact Signa, and 'describe the business and the work they want help with' hints at what to include. There is no explicit when-to-use versus when-not framing, no prerequisite checks, and no mention of what to do if the request is out of scope.

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