Skip to main content
Glama
Sign In
Healthier-Business

Hub MCP server

by Healthier-Business
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

hb_call_operation

Read-onlyIdempotent

Calls a Hub API v2 operation by ID, validates the request against the API spec, and returns only selected fields; GET requests run, writes are refused.

Instructions

[LIVE Hub] Call any Hub API v2 operation by id. Validates against the spec before sending; adds an Idempotency-Key to writes; follows pagination with all_pages (capped). The server is READ-ONLY: only GET operations run; writes are refused. Put path parameters in path_params, filters in query, JSON in body. Use fields (dotted paths such as ["candidate_ref","name"]) to keep answers small. Credits are units; money is integer pence with a currency. Never ask the user for an API key in chat.

Input Schema

NameRequiredDescriptionDefault
bodyNoJSON request body (object). For file uploads use {"filename","content_base64","content_type"} for file fields.
queryNoQuery parameters, e.g. {"per_page":50,"search":"jane"}.
fieldsNoKeep only these dotted paths of each record in `data`.
confirmNoLive writes only: true after the user approved the plan.
headersNoOnly headers the operation declares (e.g. Idempotency-Key). Authorization is never settable.
all_pagesNoList operations: fetch following pages and merge data.
max_pagesNoWith all_pages: pages to fetch (default 5, max 20).
path_paramsNoValues for {placeholders} in the path, e.g. {"candidate_ref":"<uuid>"}.
operation_idYesOperation id from hb_search_operations, e.g. hub.candidates.list.
idempotency_keyNoReuse the key from a plan or an earlier unknown-outcome write to repeat it safely.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses spec validation, idempotency-key handling, capped pagination behavior, the read-only server restriction, parameter placement rules, field projection, money/credit conventions, and API-key hygiene. Although the write-related language creates slight internal tension, it resolves explicitly to the read-only behavior declared by the annotations.

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 dense but front-loaded, starting with purpose and then covering behavior and parameter guidance. It is appropriately sized for a complex dispatcher, though it mixes protocol behavior, safety constraints, and data conventions into one compact paragraph.

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?

For a 10-parameter generic API dispatcher with no output schema, the description covers the essential invocation model, read-only behavior, pagination, and field reduction. It does not explain the return shape or error behavior, and it could more explicitly route the agent to hb_describe_operation before calling an unfamiliar operation.

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?

Schema coverage is 100%, so the schema already documents each parameter. The description still adds useful cross-parameter context, including how path/query/body values map, dotted `fields` paths, and the convention that credits are units while money is integer pence with a currency.

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 opens with a specific verb and resource: 'Call any Hub API v2 operation by id.' It clearly distinguishes this generic dispatcher from sibling tools such as hb_search_operations and hb_describe_operation by making the operation id the central input.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear operational constraints: the server is read-only, only GET operations run, and writes are refused. It also explains where to put path parameters, filters, JSON body, and how to use fields/all_pages, but it does not explicitly name sibling alternatives such as hb_describe_operation for inspecting an operation first.

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