Skip to main content
Glama
ask-aayan

ask-aayan

Skills and languages

get_skills
Read-onlyIdempotent

Retrieves Aayan's CV skills grouped by domain and spoken language levels; filter by group or return all. Use it to answer candidate skills and language questions.

Instructions

His skills grouped as on his CV (AI & LLM, Automation & Integration, Software Engineering, DevOps & Cloud, Data & ML, Ways of working) plus spoken languages with levels.

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

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: "en" (default) or "de" for German.
groupNoPart of a group name, e.g. "devops" or "ai". Omit for all groups.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without description help. The description contributes the content shape (grouped skills, languages with levels), which is useful, but says nothing about whether results are static or how the response is arranged. With annotations carrying the behavioral burden, a 3 is appropriate.

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?

A single compact sentence with no filler, and the group enumeration is front-loaded where it is most useful. The telegraphic phrasing ('His skills grouped as on his CV') is slightly awkward but does not impede comprehension.

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 two-parameter, zero-required, read-only tool with full schema coverage and annotations, the description supplies the missing piece: what the response contains. No output schema exists, so a brief note on return structure would have made it fully complete, but nothing essential to invocation is absent.

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 baseline is 3. The description does add value by listing the actual group names (DevOps & Cloud, AI & LLM, etc.), which lets an agent construct a meaningful `group` substring without guessing, but it never mentions the `lang` parameter that controls answer language.

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 (skills plus spoken languages) and enumerates the six CV groups, so an agent knows exactly what comes back and can distinguish it from get_experience or get_contact. It relies on the 'get_skills' name for the verb rather than stating an action, which keeps it just 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 Guidelines2/5

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

There is no guidance on when to call this versus sibling profile tools, nor any mention of prerequisites or the optional group filter as a narrowing strategy. The only usage signal is implied ('as on his CV'), which the agent must infer.

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