Skip to main content
Glama

contact

Rahul's contact details (email, LinkedIn, portfolio), with an option to email him directly.

Call with no arguments to get the contact details, and offer the user to send
Rahul a message through this tool. Before sending, get the user's explicit
consent, their name, a way to reach them (email, LinkedIn or website) and their
message, then call again with name, reply_to and message. Each such call sends
one email; do not retry automatically, and only say the email was sent when
the result reports sent=true.

Args:
    name: The sender's name.
    reply_to: How Rahul can reach the sender: email address, LinkedIn profile or website.
    message: The message or introduction to send Rahul.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
messageNo
reply_toNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A5/5.0
Behavior5/5

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

No annotations exist, so the description carries the full burden — and it does: one email per call, do not retry automatically, and only claim success when the result reports sent=true. It also discloses the consent requirement, which is critical for a tool that sends communications on the user's behalf.

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?

The two opening sentences carry the full workflow and are front-loaded; the Args block is the only place parameter meaning exists given 0% schema coverage, so it earns its space. Nothing is redundant with structured fields.

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

Completeness5/5

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

An output schema exists, so return-format details are unnecessary, yet the description still flags the one result field that matters (sent=true). Combined with the consent workflow, retry prohibition and parameter meanings, an agent has everything needed to call this correctly and report accurately.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate, and it does: name is the sender's name, reply_to accepts an email address, LinkedIn profile or website, and message is the introduction to send. It also clarifies that all three are effectively required to send despite the schema defaulting them to empty strings.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states two concrete capabilities with specific verbs and resources: returning Rahul's contact details (email, LinkedIn, portfolio) and sending him an email. An agent can immediately distinguish this from the sibling tools (education, experience, overview, patents, projects, skills), which are all read-only portfolio sections.

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

Usage Guidelines5/5

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

It gives explicit routing rules: call with no arguments for details, then offer the messaging option, and call again with name/reply_to/message to send. It also states preconditions (obtain explicit user consent plus their name, contact channel and message) before the send call — clear when-to-use guidance with no inference required.

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