Skip to main content
Glama
Sign In
ModelRouter MCP

ModelRouter MCP

by MrSolution07
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sync_metadata

Synchronizes model metadata from external sources to keep recommendations current. Blocks automatically in privacy mode.

Instructions

Sync model metadata from external sources. Blocked in privacy mode.

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

Input Schema

NameRequiredDescriptionDefault
configNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided; description asserts a sync operation and privacy restriction but does not disclose side effects, authentication needs, or what happens to existing data.

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 with no wasted words. Purpose is front-loaded, constraint follows immediately.

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?

Lacks details on parameter usage, return values, error conditions, or usage context. Incomplete for a tool with a vague parameter and no annotations.

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?

Single parameter 'config' is an object with no schema description or constraints. The description adds no meaning about its structure, keys, or expected values.

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?

Clearly states verb (sync), resource (model metadata), and source (external). Adds constraint (blocked in privacy mode), distinguishing it from analysis and recommendation siblings.

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

Usage Guidelines2/5

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

Mentions a condition when not to use (privacy mode) but provides no guidance on when to use this tool vs. alternatives or prerequisites.

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