VibeServe

by ncsound919

Overview Schema Source Related Servers Discussions Admin

Hybrid

memory_stats

Retrieve statistics on learned and stored UI specifications to assess data patterns and coverage.

Instructions

Get statistics on learned/stored UI specifications

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ctx": "<ctx>"
    },
    "name": "memory_stats"
  }
}

Input Schema

Name	Required	Description	Default
`ctx`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Jun 17, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, and the description only states 'Get statistics', implying a read-only operation. It does not disclose any side effects, cost implications, or specifics about the statistics returned (beyond an output schema that is not described). The minimal description fails to add behavioral context beyond the obvious.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no unnecessary words. It is front-loaded with the action and resource. However, it is too brief, sacrificing completeness for conciseness.

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?

Given the tool has one undocumented parameter and an output schema that is not referenced, the description is incomplete. It does not explain what 'ctx' is or what statistics are returned. Although the output schema exists, the description should still guide the agent on proper usage.

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?

The input schema has one required parameter 'ctx' with no description (schema description coverage 0%). The tool description provides no information about this parameter, leaving the agent to guess its purpose or allowed values. This is a critical gap for a single-parameter tool.

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 states the tool retrieves statistics about learned/stored UI specifications, specifying the verb 'Get' and the resource 'statistics on learned/stored UI specifications'. It is distinct from sibling tools like 'list_design_systems' which list design systems, not memory stats.

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?

No guidance is provided on when to use this tool versus alternatives such as 'list_design_systems' or 'vibe_health'. The description does not indicate any prerequisites or context for use, leaving the agent without decision-making support.

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