Skip to main content
Glama

list_values

List valid values for a chosen dimension, such as species, country, or lab, with the number of tests for each. Use it to explore which categories exist in the livestock health graph.

Instructions

List the valid values of one dimension with the number of tests for each. dimension: species, pathogen, country, lab, breed, sample_type, diagnostic_test or production_stage.

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

Input Schema

NameRequiredDescriptionDefault
dimensionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose the return payload (values accompanied by test counts), which is real behavioral information. However, it says nothing about whether counts are global or scope-dependent, whether results are ordered, or whether the operation is read-only.

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?

Two sentences, front-loaded with the purpose, and the value list follows immediately. Every element is load-bearing: the second line is the only place the allowed dimension names appear.

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 single-parameter, non-destructive tool with no output schema, the description supplies both the input domain and the shape of the result, which is close to sufficient. The absence of any annotation means a note on read-only nature or count scoping would have closed the remaining gap.

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?

Schema coverage is 0% and the schema declares 'dimension' as an unconstrained string with no enum, so the description's enumeration of the seven legal values (species, pathogen, country, lab, breed, sample_type, diagnostic_test, production_stage) is the only source of that closed set. It stops short of noting case sensitivity or whether other dimensions exist, so not a 5.

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

Purpose4/5

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

"List the valid values of one dimension with the number of tests for each" gives a specific verb (list) and resource (dimension values plus counts), so the agent knows exactly what comes back. It does not name or differentiate itself from siblings such as describe_term or search_terms, which keeps it from a 5.

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 enumerated dimension list implies the discovery/facet-counting use case, but the description never states when to choose this over describe_term or search_terms, nor any prerequisite. Usage is inferable rather than stated.

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