Skip to main content
Glama
Sign In
hackle-mcp

hackle-mcp

Official
by hackle-io
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Remote

remote-config-update-description

Modify remote config descriptions in both production and development environments for proper documentation and consistency across Hackle API A/B test configurations.

Instructions

Updates remote config's description. The change will be applied to both production and development environment.

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": {
      "remoteConfigId": "<remoteConfigId>",
      "body": "<body>"
    },
    "name": "remote-config-update-description"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
remoteConfigIdYesRemote config's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the change applies to 'both production and development environment', which adds some context about scope, but lacks details on permissions, side effects, error handling, or response format. For a mutation tool with zero annotation coverage, this is insufficient.

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 front-loaded and concise with two sentences that directly state the action and scope. There's no wasted text, making it efficient and easy to parse.

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's complexity (mutation with 2 parameters, no output schema, and no annotations), the description is incomplete. It lacks details on behavioral traits, parameter usage, and output expectations, making it inadequate for safe and effective tool invocation.

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 description coverage is 50% (only 'remoteConfigId' has a description), and the description doesn't add meaning beyond the schema. It implies parameters for updating a description but doesn't explain 'body' or 'description' fields. With low coverage, the description fails to compensate, resulting in a baseline score.

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 action ('Updates') and resource ('remote config's description'), making the purpose evident. However, it doesn't differentiate from sibling tools like 'remote-config-update' or 'remote-config-update-user-identifier-criteria', which would require more specificity about what exactly this tool updates versus those.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, compare with siblings like 'remote-config-update' or 'remote-config-create', or specify scenarios where this tool is appropriate, leaving usage unclear.

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

Related Tools