Skip to main content
Glama
Sign In
casemgr-mcp

casemgr-mcp

by mstang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

meta-embeddings_stats

meta-embeddings_stats

Retrieve statistics on semantic search embeddings, including total count, counts by type, and enablement status.

Instructions

Returns statistics about semantic search embeddings: total count, counts by type, and whether embeddings are enabled.

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": "meta-embeddings_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes the read-only nature implicitly by stating 'Returns statistics', but does not explicitly confirm no side effects or destructive actions. The behavioral disclosure is adequate but not explicit.

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 a single sentence that is perfectly concise. It front-loads the key action 'Returns statistics' and quickly enumerates the outputs. 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?

With no parameters and no output schema, the description is fairly complete. It tells the agent exactly what the tool returns (total count, counts by type, enabled status). The format is not specified, but the summary is sufficient for a simple tool.

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?

There are no parameters in the input schema, so schema coverage is 100%. The baseline for zero parameters is 4, and the description adds no additional parameter information, which is acceptable given there are none.

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 it returns statistics about semantic search embeddings, specifying exact outputs: total count, counts by type, and enabled status. The verb 'returns' and resource 'statistics about embeddings' are specific and unambiguous.

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 usage when embedding statistics are needed, but does not explicitly state when to use this tool over siblings like meta-embeddings_backfill or meta-tool_stats. No exclusions or alternatives are mentioned.

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