Skip to main content
Glama
ask-aayan

ask-aayan

Contact details

get_contact
Read-onlyIdempotent

Retrieve Aayan's email, LinkedIn, GitHub, portfolio, CV PDF link, and location when you need to contact him or review his CV.

Instructions

How to reach him: email, LinkedIn, GitHub, portfolio, a link to his CV as PDF, and his location. Use when someone wants to contact him or see his CV.

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": "get_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description's only added value is enumerating the fields returned (including a CV PDF link and location), which is genuinely useful since there is no output schema, but it says nothing about whether the data is static or how stale it may be.

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 short sentences, front-loaded with what is returned and followed by the trigger condition. Nothing is padded and no sentence is wasted.

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?

For a zero-argument read tool with full annotation coverage and no output schema, describing the returned channels is largely sufficient. A brief note that the links are static profile data would close the remaining gap, but an agent has enough to call it correctly.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline applies. The description correctly avoids inventing inputs.

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 names the resource (contact channels) and enumerates the specific fields returned: email, LinkedIn, GitHub, portfolio, a CV PDF link, and location. It is clearly distinguishable from content-oriented siblings like get_experience or get_skills, though it never states a verb (e.g., 'returns') and refers to the subject only as 'him'.

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?

'Use when someone wants to contact him or see his CV' gives an explicit, concrete trigger condition, which is unusually good for a zero-argument tool. It offers no exclusions or pointers to alternatives, but for a single-purpose contact lookup there is little ambiguity to resolve.

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