Skip to main content
Glama
Sign In

Symmap

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Symmap Ingredient

symmap_ingredient
Read-onlyIdempotent

One Traditional Chinese Medicine ingredient (molecule) from SymMap v2 (symmap.org): its protein targets with literature evidence (PubMed-cited edges are tier "laboratory", uncited ones "computational_prediction") and the herbs it has been identified in. A target association is a molecular finding or a prediction — NOT evidence the ingredient treats any condition.

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": {
      "ingredient": "quercetin",
      "herbs_limit": 3,
      "targets_limit": 3
    },
    "name": "symmap_ingredient"
  }
}

Input Schema

NameRequiredDescriptionDefault
ingredientYesIngredient name (e.g. "quercetin") or SMIT id (SMIT00013)
herbs_limitNoMax source herbs returned, 1-200 (default 25)
targets_limitNoMax protein targets returned, 1-200 (default 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description adds important behavioral context: PubMed-cited edges are tiered 'laboratory', uncited ones are 'computational_prediction', and target associations are explicitly not evidence that an ingredient treats any condition. This materially helps the agent interpret results safely.

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 two dense sentences with no filler. It front-loads the resource and both return categories, then adds the critical interpretive caveat in a separate sentence.

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 read-only lookup tool with simple, fully documented parameters, the description covers the resource, output categories, evidence semantics, and a domain-critical caveat. No output schema exists, but the description gives enough about the returned data for an agent to use it correctly.

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 100%, so the baseline is 3, but the description adds meaning by clarifying that 'targets' refers to protein targets with literature-evidence tiers and that herbs are the herbs in which the ingredient was identified. This enriches the otherwise minimal schema descriptions for herbs_limit and targets_limit.

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?

The description clearly identifies the resource as a single TCM ingredient and specifies that the tool returns its protein targets and source herbs. It distinguishes ingredient-centric scope from herb-centric siblings like symmap_herb, though it lacks an explicit retrieval verb and does not name an alternative sibling.

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 when to use the tool: for ingredient-centric queries about targets and herbs. However, it provides no explicit comparison to sibling tools such as symmap_herb, symmap_herb_ingredients, or symmap_search, and no exclusions are stated.

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

All Symmap toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources