Skip to main content
Glama
Sign In
mcp-github-advanced-search

mcp-github-advanced-search

by louiscklaw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

git_helloworld

Send a test input to confirm the MCP server responds correctly, validating your GitHub advanced search integration setup.

Instructions

my helloworld call

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

Input Schema

NameRequiredDescriptionDefault
test_inputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.2

TDQS

D1/5.0
Behavior1/5

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

With no annotations and a description that reveals nothing about side effects, permissions, return values, or any behavioral traits, an agent is completely blind to what happens when this tool is invoked. The description adds zero value beyond the tool name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While short, this is under-specification rather than conciseness. The sentence 'my helloworld call' carries no operational information and does not earn the little space it occupies.

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

Completeness1/5

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

For a tool with a required parameter and no output schema or annotations, the description should compensate. It provides nothing, making the tool unusable for an agent without external knowledge.

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

Parameters1/5

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

The schema has one required parameter test_input with no description, and schema description coverage is 0%. The description does not explain what test_input means, its format, or its purpose, leaving the agent entirely unguided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'my helloworld call' is essentially a tautology of the tool name git_helloworld. It provides no specific verb, resource, or scope, and gives an agent no way to understand what the tool actually does or how it differs from siblings.

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

Usage Guidelines1/5

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

The description offers no guidance on when to use this tool vs. alternatives. Sibling tools like gas_entrypoint and gas_search_code exist, but there is no mention of them or any conditions for selecting this tool.

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