Skip to main content
Glama
Sign In
moates-mcp

moates-mcp

by moates695
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

search

Search Marcus Oates' profile, projects, experience, and skills using keywords. Retrieves snippets with source citations for accurate fact attribution.

Instructions

Keyword-search everything about Marcus (experience, projects, skills).

Returns matching snippets with a source label so the model can cite where a fact came from.

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

Input Schema

NameRequiredDescriptionDefault
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, description carries full burden. It discloses that it returns 'matching snippets with a source label' and describes the read-only nature. No destructive behavior mentioned, which is appropriate for a search tool.

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 sentences, front-loaded with purpose, followed by return information. No unnecessary words. Highly efficient.

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

Completeness5/5

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

Given the output schema exists (so return values are defined), siblings are specific, and the tool has one parameter, the description fully covers the necessary context for an agent to select and invoke it correctly.

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 has 0% description coverage for the 'query' parameter. Description adds the meaning of 'keyword-search' and 'matching', providing some semantic clarification beyond the schema's 'Query' title, but lacks specifics like format or examples.

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 'keyword-search everything about Marcus (experience, projects, skills)', which is a specific verb+resource combination. It distinguishes from sibling tools which are targeted getters for specific sections.

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?

Usage context is implied: use for cross-domain search rather than fetching specific sections. However, no explicit when-to-use, when-not-to-use, or alternative names are provided.

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