Skip to main content
Glama

dislop

dislop_voice_extract

Extract a reusable dislop.voice/1 style profile from 1-5 human writing samples (2 credits, requires Bearer dslp_* token).

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": {
      "samples": "<samples>"
    },
    "name": "dislop_voice_extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
samplesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full load; it does disclose auth (Bearer dslp_* token) and cost (2 credits) and caps input at 1-5 samples, which is genuinely useful pre-call context. It says nothing about what happens to the submitted samples, whether the profile is persisted or returned, or failure/validation behavior.

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?

One dense sentence with the core action front-loaded and payment/auth constraints tucked into a parenthetical; nothing is wasted. The parenthetical is slightly overloaded but still readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-annotation tool with no output schema and a named output format (dislop.voice/1), the agent still lacks any statement of what comes back, whether the profile is stored, and what `lang` does. Cost and auth are covered, so it is adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate for two parameters. It covers `samples` well (count range and that they must be human writing), but `lang` (zh/en enum) is never mentioned, so roughly half the parameter surface is undocumented.

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?

States a specific verb (Extract) and a specific artifact (a reusable dislop.voice/1 style profile) plus the source (1-5 human writing samples). That is clearly distinguishable from check/deslop/explain/packs/review siblings by resource, though it never names an alternative explicitly.

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?

Implies the usage context (you have 1-5 human writing samples and want a reusable style profile) and adds real invocation constraints: sample count range, 2 credits, and a Bearer dslp_* token requirement. It gives no explicit when-not-to-use or pointer to a sibling that handles a related job.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.