TogoMCP

Overview Schema Source Related Servers Discussions Admin

togoid_countId

Read-only

Count how many source IDs have mappings in a target database before bulk conversion, verifying format and estimating result size.

Instructions

Check how many of your IDs can be converted before doing bulk conversion.

A lightweight pre-check: tells you how many source IDs have mappings in the target database WITHOUT actually returning the mapped IDs. Use this to: - Verify your IDs are in the correct format - Estimate result size before a large convertId call - Check if a conversion route works for your specific IDs

This is a single-hop, pairwise check: pass source and target as two separate args (unlike convertId, which takes one comma-joined route).

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": {
      "source": "<source>",
      "target": "<target>",
      "ids": "<ids>"
    },
    "name": "togoid_countId"
  }
}

Input Schema

Name	Required	Description
`ids`	Yes	Source IDs to check. Accepts either a list of strings or a comma-separated string (e.g., ["672", "675"] or "672,675").
`source`	Yes	Source database key (e.g., 'ncbigene', 'uniprot')
`target`	Yes	Target database key (e.g., 'uniprot', 'pdb')

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.0.0Jul 25, 2026

addedInput schema / properties / ids / description

Added value: +"Source IDs to check. Accepts either a list of strings or a\ncomma-separated string (e.g., [\"672\", \"675\"] or \"672,675\")."

addedInput schema / properties / source / description

Added value: +"Source database key (e.g., 'ncbigene', 'uniprot')"

addedInput schema / properties / target / description

Added value: +"Target database key (e.g., 'uniprot', 'pdb')"

First observedv0.1.0Jun 11, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, but the description adds valuable behavioral context: it is a lightweight pre-check, it does NOT return mapped IDs, and it is a single-hop pairwise check. This goes beyond what annotations provide and clarifies the tool's side-effect-free, non-returning nature.

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?

The description is well-structured and front-loaded with the core purpose, followed by a concise bulleted list of use cases and a final clarifying note about parameter style. Every sentence adds value without unnecessary fluff.

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, the annotations are present, and all parameters are documented in the schema, the description fully covers the tool's purpose, usage context, behavioral constraints, and relationship to the sibling convertId tool. No critical gaps remain.

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 input schema already documents all three parameters with 100% coverage, so the baseline is 3. The description adds meaning by explaining that source and target are passed as two separate args and that this is a single-hop pairwise check, which clarifies the parameter relationship and distinguishes it from convertId's route parameter.

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's function: 'Check how many of your IDs can be converted before doing bulk conversion.' It specifies the resource (source IDs, target database) and explicitly distinguishes itself from the sibling togoid_convertId by highlighting that this is a pre-check that does not return mapped IDs.

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

Usage Guidelines5/5

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

The description provides explicit use cases: verify ID format, estimate result size before a large convertId call, and check if a conversion route works. It also contrasts this tool with convertId's comma-joined 'route' parameter, giving clear guidance on when to use this tool versus the alternative.

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