protein-tools-mcp

Overview Schema Source Related Servers Discussions Admin

cache_info

Inspect or clear the local response cache used by UniProt, AlphaFold DB, and RCSB lookup tools to manage stored results.

Instructions

Inspect (or with clear=True, empty) the local response cache used by the premium lookup tools (UniProt / AlphaFold DB / RCSB).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cache_info"
  }
}

Input Schema

Name	Required	Description	Default
`clear`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the key behavioral trait — that clear=True empties (mutates/destroys) the cache — which is real value. However it says nothing about consequences of clearing (lost responses, re-fetch cost), permissions, or irreversibility.

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?

One tightly written sentence, front-loaded with the primary action, with the destructive variant clearly bracketed. No wasted words.

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 utility with an output schema (so return values needn't be explained), this is nearly complete: it names what is cached and the clear behavior. A brief note on whether clearing is safe/reversible would close 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 single 'clear' boolean has no schema description, so the description must compensate — and it does, explaining that clear=True empties the cache (default False = inspect). That is the essential semantics for the only 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?

States a specific verb ('Inspect'/'empty') and resource ('local response cache'), and scopes it to the premium lookup tools (UniProt / AlphaFold DB / RCSB). No sibling tool touches the cache, so the agent can identify this uniquely from the name plus description.

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 parenthetical 'with clear=True, empty' implies the two usage modes, but there is no explicit when-to-use guidance, no statement of when clearing is appropriate, and no exclusions or alternatives named. Usage is only implied.

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