Skip to main content
Glama

togoid_getDataset

Read-only

Retrieve configuration details for a specific biological database, including ID format, URI prefix, example IDs, and available annotations, to validate and prepare identifiers before bulk conversion.

Instructions

Get configuration for a specific database in TogoID.

Retrieves detailed metadata about a single dataset, including its ID format, URI prefix, example IDs, and available annotations.

RETURNS a dict with label (human-readable name), regex (ID-validation pattern — use it to check your IDs are well-formed), prefix (URI prefixes for linking), examples (sample IDs — test with countId before bulk conversion), and annotations (available annotation types).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
datasetYesDataset key (e.g., 'uniprot', 'ncbigene', 'pdb', 'chembl_target', 'ensembl_gene', 'hgnc', 'pubchem_compound')

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already signal read-only and open-world behavior. The description adds valuable behavioral context: `regex` should be used to validate IDs, and `example` IDs should be tested with `countId` before bulk operations. It does not contradict the annotations.

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

Conciseness4/5

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

The description is well-structured and front-loaded with the tool's purpose. The return field explanation is useful and avoids serious filler. It is moderately detailed, but each part earns its place.

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?

For a single-parameter, read-only metadata retrieval tool with annotations and an output schema, the description is complete. It explains what is returned, how to interpret the fields, and how the returned data can be used in combination with `togoid_countId`.

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?

The input schema already documents the `dataset` parameter completely, including example values, and coverage is 100%. The description adds some contextual meaning around returned fields like `regex` and `examples`, but it does not deeply expand the dataset parameter semantics beyond what the schema provides.

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 it retrieves configuration/metadata for a specific dataset in TogoID, using a specific verb and resource. It explicitly distinguishes from the sibling tool `togoid_getAllDataset` by emphasizing 'specific database' and 'single dataset'.

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?

The description implies usage for inspecting a single dataset's metadata and mentions using `countId` for testing before bulk conversion. However, it does not explicitly tell the agent when to prefer this tool over siblings like `togoid_getAllDataset` or `togoid_getDescription`.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dbcls/togomcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server