Skip to main content
Glama

Mygene Info Metadata

mygene_info_metadata
Read-onlyIdempotent

Release / source metadata.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mygene_info_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
srcNoSource database metadata
versionNoAPI version
timestampNoMetadata timestamp

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that—it does not say which release or source is reported, whether the value is static or changes over time, or why an agent would want it. With an output schema present, return format is excused, but the semantic content is still absent.

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

Conciseness2/5

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

The text is a four-word fragment with no sentence structure and no front-loaded explanation of what the metadata contains. It is short without being concise—under-specification rather than economy—so brevity here does not earn credit.

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?

The surrounding structure is favorable: no parameters, full schema coverage, a rich annotation set, and an output schema that documents the return value. Against that low burden the description is still thin, but an agent can call it correctly (no arguments) and the output schema tells it what comes back, so the gap is moderate rather than crippling.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate. Per the zero-parameter baseline, a 4 is appropriate; the description is not required to compensate for any schema gap.

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

Purpose2/5

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

"Release / source metadata" is a noun fragment that essentially restates the tool name (mygene_info_metadata) without a verb or scope. It hints at the resource (release/source provenance) but an agent cannot tell from this what is actually returned or how it differs from sibling tools like mygene_info_gene or mygene_info_query.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The description neither excludes cases nor points to sibling tools, leaving the agent to infer that this is a provenance-lookup call from the name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.