Skip to main content
Glama
Sign In
cxg-census-mcp

cxg-census-mcp

by MaxMLang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_available_values

List distinct values for a cell metadata column, filtered by organism and prefix, to discover available terms before using resolve_term.

Instructions

Distinct values for an obs column (discovery before resolve_term).

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": {
      "column": "<column>"
    },
    "name": "list_available_values"
  }
}

Input Schema

NameRequiredDescriptionDefault
columnYes
organismNohomo_sapiens
prefixNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.8/5.0
Behavior2/5

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

No annotations provided, so description must cover behavioral traits. It only states it lists distinct values, implying a read operation, but misses details like performance limits, error conditions, or any side effects.

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?

Single sentence with front-loaded purpose and a contextual hint. Efficient but risks being too terse for agents unfamiliar with the domain.

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

Completeness2/5

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

No output schema, no annotations, and incomplete parameter semantics. The description omits return format, pagination, error handling, and the relationship to the 'obs' concept. Lacks completeness for reliable invocation.

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?

Schema description coverage is 0%, and the description adds no information about what parameters like 'column', 'organism', 'prefix', or 'limit' mean. Agent fully reliant on schema types, which are insufficient.

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?

Clearly states it returns distinct values for an obs column, and the parenthetical 'discovery before resolve_term' provides context on its role in a workflow. However, 'obs column' is jargon that may not be immediately clear to all agents.

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?

Implies usage before resolve_term, but does not explicitly state when to use this tool vs siblings like expand_term or term_definition. No guidance on when not to use it.

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