Skip to main content
Glama
ask-aayan

ask-aayan

Work experience

get_experience
Read-onlyIdempotent

Retrieve Aayan's work history newest first, including dates, locations, and accomplishments; filter by company or skill to answer questions about where he worked and what he did.

Instructions

His jobs, newest first, with dates, location and what he built in each. Filter by company (e.g. "Teamworks") or by a skill or technology (e.g. "n8n", "LDAP"). Use for questions about where he worked and what he did there.

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

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: "en" (default) or "de" for German.
skillNoA skill or technology used in the job, e.g. "n8n", "Azure", "React".
companyNoPart of a company name, case-insensitive, e.g. "teamworks" or "gini".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the description only needs to add retrieval shape. It does add useful context: result ordering (newest first) and the fields returned (dates, location, accomplishments), which matters because no output schema exists. It does not cover pagination, result limits, or what an empty filter result looks like.

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?

Three short sentences: what is returned and in what order, how to filter, and when to reach for it. The most important information (the resource and its ordering) is front-loaded and nothing is redundant.

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 compensates by describing return content and ordering, and it explains both free-text filters. The only residual gap is the lang parameter and any notion of result size or pagination for a potentially multi-job history.

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%, so baseline is 3. The description's filter examples for company and skill largely restate the schema's own examples ("teamworks", "n8n"), adding only a little ("LDAP"), and the lang parameter is never mentioned in the description at all.

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 concrete resource (his jobs) plus ordering (newest first) and returned content (dates, location, what he built in each), which is far more specific than a restatement of the name. It stops short of naming which sibling to prefer for adjacent topics like projects or skills, so differentiation is implied by subject matter rather than stated.

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 for questions about where he worked and what he did there' gives a clear triggering context, and the filter examples show two entry paths (company vs. skill/technology). It offers no explicit exclusions or named alternatives such as get_projects or get_skills, so an agent must infer the boundary itself.

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