Skip to main content
Glama
ask-aayan

ask-aayan

Projects

get_projects
Read-onlyIdempotent

Retrieves Aayan’s shipped projects—production, personal R&D, and university work—with role, results, and stack, and filters by tag to answer “what has he shipped?”

Instructions

Projects he built (production work, personal R&D, university), each with what it does, his role, results and stack. Filter by tag, e.g. "voice", "extraction", "on-prem", "automation", "rag". Use for "what has he shipped" questions.

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

Input Schema

NameRequiredDescriptionDefault
tagNoOne tag, e.g. "voice", "extraction", "on-prem", "automation", "n8n", "llm", "rag", "full-stack". An unknown tag returns the list of tags.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real value beyond that by describing what each returned project contains (role, results, stack) and that tags are the filter axis; the unknown-tag fallback lives in the schema rather than the description.

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 tight sentences: the first establishes what the resource is and what each item contains, the second gives filtering and the question type it answers. No filler, and the most important content is front-loaded.

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 single-optional-parameter read tool with full annotation coverage, the description covers purpose, filtering, and returned fields. Only minor gaps remain, such as result ordering or volume, and no output schema exists to defer to.

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 schema itself documents the tag parameter, its examples, max length, and the unknown-tag fallback. The description largely repeats the same tag examples without adding new semantics, so baseline 3 applies.

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 uses a clear verb+resource framing ("Projects he built") and spells out the content of each entry (what it does, his role, results, stack). The phrase "Use for 'what has he shipped' questions" carves out a distinct use case versus siblings like get_experience or get_skills, though no sibling is named explicitly.

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?

It states clearly when to reach for this tool ("what has he shipped" questions) and explains the filtering dimension with concrete tag examples. It does not say when to prefer get_experience or search_profile instead, so routing is only partially covered.

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