Skip to main content
Glama
ask-aayan

ask-aayan

Search his profile

search_profile
Read-onlyIdempotent

Search a candidate's full profile by keyword to return section-labelled snippets for specific technologies, domains, or claims not covered by other lookup tools.

Instructions

Keyword search across his whole profile (summary, jobs, projects, lab demos, education, skills, availability, contact). Returns matching snippets labelled with their section. Use for a specific technology, domain or claim that the other tools do not answer directly.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of snippets, 1 to 25. Default 8.
queryYesKeywords, e.g. "voice agents", "LibreChat", "row-level security". Not a full question.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/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 the safety profile is covered. The description adds useful behavior in the form of the return shape ('matching snippets labelled with their section'), but says nothing about empty-result handling, ranking, or truncation when limit is hit.

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 scope and followed by the return format and routing hint. The parenthetical section list is slightly long but earns its place by showing what the search spans relative to the per-section getters.

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 two-parameter read tool with full schema coverage, no output schema, and rich annotations, the definition is nearly sufficient. The only real gap is the unexplained possessive 'his' (whose profile) and no mention of behavior when nothing matches.

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 both `query` and `limit` are already documented with bounds and examples, including the note that query is keywords, not a full question. The description adds no syntax, tokenization, or limit-tuning guidance beyond that baseline.

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 specific verb and resource ('Keyword search across his whole profile') and enumerates the covered sections (summary, jobs, projects, skills, availability, contact), which maps onto the get_* sibling tools. It stops short of naming those siblings explicitly, so the distinction is conveyed implicitly rather than crisply.

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?

Gives a clear selection rule: use it for 'a specific technology, domain or claim that the other tools do not answer directly', which positions it as the fallback to the section-specific getters. There is no explicit when-not statement, but the fallback framing implies the alternatives.

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