Skip to main content
Glama
Sign In
my-mcp-server

my-mcp-server

by jason-bourne-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

has_skill

Check whether Aniket has a specific skill by retrieving supporting evidence from his resume and experience.

Instructions

Check whether Aniket has a given skill and return supporting evidence from his skills and experience.

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": {
      "skill": "<skill>"
    },
    "name": "has_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
skillYesSkill or technology, e.g. 'Kafka', 'RAG', 'Kubernetes'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Discloses that it returns 'supporting evidence from his skills and experience', but does not detail the format or structure of the evidence. No annotations are provided, so the description bears full responsibility but offers only general behavior.

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?

Single sentence, front-loaded with verb and resource, no extraneous words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple check tool with one parameter and no output schema, description conveys purpose and return type (evidence) but lacks details on the format of the evidence, which could help an agent parse the response.

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 already describes the 'skill' parameter with examples. Description adds no new parameter-level information beyond tool purpose, so baseline of 3 is appropriate.

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?

Description clearly states the verb 'check', the resource 'skill', and the scope 'Aniket's skills and experience'. It distinguishes from siblings like 'get_skills' which likely lists all skills, and 'search_background' which is broader.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Implies usage: to verify a specific skill with evidence. No explicit when-not-to-use or alternatives are named, but the context of sibling tools provides some differentiation.

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

Deploy Server

Other Tools