Skip to main content
Glama
Sign In
cdtm-mcp

cdtm-mcp

by htahir1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

refresh_taxonomy

Re-fetch the filter taxonomy from the portal to update stale tags and keep member search categories current.

Instructions

Re-fetch the filter taxonomy from the portal (use if tags seem stale).

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": "refresh_taxonomy"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior2/5

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

There are no annotations, so the description carries the full burden. It merely says 're-fetch' without disclosing side effects (e.g., whether it mutates local state, makes external network calls, or blocks). This is minimal behavioral disclosure for a tool that likely has an update-like side effect.

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?

A single, front-loaded sentence communicates purpose and usage guidance with no filler. Every word contributes value.

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 zero-parameter tool with an output schema, the description is sufficient: it states what the tool does and when to use it. It does not need to explain return values due to the output schema, though it could mention any blocking or performance implications.

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?

The tool has 0 parameters, so per the rubric the baseline is 4. The description correctly implies there are no configurable inputs and focuses on the action itself.

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 the tool's verb ('re-fetch'), resource ('filter taxonomy'), and source ('from the portal'). It distinguishes itself from sibling tools (list_tag_categories, list_tags) which are read/list operations, whereas this is a refresh operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a clear usage trigger: 'use if tags seem stale.' This provides context on when to invoke this tool, though it does not explicitly contrast with alternatives or mention 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