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

my-mcp-server

by jason-bourne-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_project

Find project details by name with partial, case-insensitive matching. Provides project information from a resume database.

Instructions

Details for one project by name (partial, case-insensitive match).

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

Input Schema

NameRequiredDescriptionDefault
nameYesProject name, e.g. 'Road Clash'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations provided, so description carries the burden. It discloses the matching behavior (partial, case-insensitive) but does not specify handling of multiple matches, no matches, or side effects. Adequate but not comprehensive.

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 key information, no wasted words.

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 get-one tool with one parameter and no output schema, the description is largely complete. It explains input and retrieval behavior. Missing details on return format or error handling, but adequate for the complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'name' has a schema description, and the tool description adds behavioral context (partial, case-insensitive), which goes beyond the schema. Schema coverage is 100%.

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?

The description clearly states the tool retrieves details for a single project by partial, case-insensitive name match, distinguishing it from sibling tools like 'get_projects' which likely returns multiple projects.

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?

The description implies usage context: when a single project's details are needed with a partial name. It does not explicitly state when not to use or mention alternatives, but the sibling tool list provides context.

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