Skip to main content
Glama
hackle-io

hackle-mcp

Official
by hackle-io

remote-config-detail

Fetch detailed information for a specific remote configuration using the provided remoteConfigId, enabling efficient querying and management of A/B test data on the Hackle MCP server.

Instructions

Fetch remote config detail.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
remoteConfigIdYesRemote config's id. You can get this information by using Remote Config List Tool.

Implementation Reference

  • The handler function that fetches the remote config detail via WebClient.get and returns JSON-stringified response as text content.
    async ({ remoteConfigId }) => {
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(await WebClient.get(`/api/v1/remote-configs/${remoteConfigId}`)),
          },
        ],
      };
    },
  • Zod input schema defining remoteConfigId as a positive number.
    {
      remoteConfigId: z
        .number()
        .positive()
        .describe("Remote config's id. You can get this information by using Remote Config List Tool."),
    },
  • src/index.ts:347-366 (registration)
    Registers the remote-config-detail tool on the McpServer with name, description, input schema, and handler.
    server.tool(
      'remote-config-detail',
      'Fetch remote config detail.',
      {
        remoteConfigId: z
          .number()
          .positive()
          .describe("Remote config's id. You can get this information by using Remote Config List Tool."),
      },
      async ({ remoteConfigId }) => {
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(await WebClient.get(`/api/v1/remote-configs/${remoteConfigId}`)),
            },
          ],
        };
      },
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Fetch' which implies a read-only operation, but doesn't clarify permissions, rate limits, error handling, or what 'detail' includes (e.g., full configuration, metadata). This leaves significant gaps for a tool that likely returns structured 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?

The description is extremely concise at three words, front-loaded with the core action ('Fetch'), and wastes no space. Every word earns its place, making it easy for an agent to parse quickly.

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 complexity (a detail-fetching tool with no output schema and no annotations), the description is incomplete. It doesn't explain what 'detail' entails, potential response formats, or error cases, which are crucial for an agent to use the tool effectively in context with siblings like list and update tools.

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 100%, with the parameter 'remoteConfigId' well-documented in the schema (including type, constraints, and a note to get it from 'remote-config-list'). The description adds no additional parameter information beyond the schema, so it meets the baseline for high coverage without compensation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Fetch remote config detail' clearly states the action (fetch) and resource (remote config detail), but it's vague about what 'detail' encompasses compared to siblings like 'remote-config-list' or 'remote-config-update'. It distinguishes the basic operation but lacks specificity about the scope of information returned.

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 explicit guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing a remoteConfigId from 'remote-config-list'), exclusions, or contextual cues, leaving the agent to infer usage from the parameter description alone.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hackle-io/hackle-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server