Skip to main content
Glama
ask-aayan

ask-aayan

Summary

get_summary
Read-onlyIdempotent

Retrieves Syed Aayan Ahmed's profile overview—headline, target role, location, current job, languages, and work belief—for answering general questions about him.

Instructions

Overview of Syed Aayan Ahmed: headline, target role, location, current job, profile paragraph, languages and his one belief about the work. Call this first for any general question about him.

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_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: "en" (default) or "de" for German.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety and side-effect behavior need no restating. Beyond that, the description discloses the shape of the payload it returns, enumerating the seven content areas, which is real added value for a tool with no output schema; it does not address language-fallback behavior or whether missing fields are omitted.

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 sentences, front-loaded with the resource and followed immediately by the call-first directive. The field enumeration is long but each item conveys distinct content, so nothing is truly wasted; a slightly tighter phrasing would earn a 5.

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 simple zero-required-parameter, read-only overview tool, the definition covers purpose, ordering advice, and return contents, which compensates for the absence of an output schema. The only gaps are edge behavior such as what happens when a field is unavailable and how the language fallback works.

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 coverage is 100% and the single `lang` enum already documents 'en' (default) and 'de' with its meaning, so the schema does the heavy lifting and the baseline of 3 applies. The description adds nothing about the parameter and its mention of "languages" refers to spoken-language content, not the `lang` selector, which could momentarily blur the two.

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 names the specific resource (an overview of Syed Aayan Ahmed) and enumerates exactly what it contains: headline, target role, location, current job, profile paragraph, languages, and a belief about the work. This is granular enough that an agent can distinguish it from the narrower siblings like get_experience or get_skills without opening any schema.

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?

"Call this first for any general question about him" is an explicit routing rule that tells the agent where to start and implicitly contrasts with the detail-oriented siblings. It lacks an explicit when-not clause (e.g., 'do not use for contact details or availability'), so it stops short of a top score.

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