Skip to main content
Glama
diblaze

bokio-mcp

by diblaze
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

bokio_raw_get

Read-only

Send a GET request to any Bokio API path not covered by other tools, replacing {companyId} with the company ID and returning the response body.

Instructions

Send a GET to any Bokio API path that no other tool covers; {companyId} in the path is replaced with the company id. Returns the response body.

Input Schema

NameRequiredDescriptionDefault
pathYesAPI path below /v1, e.g. /companies/{companyId}/tag-groups; query values go in params
paramsNoScalar query params
companyIdNoBokio company id. Defaults to BOKIO_COMPANY_ID if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.6.0
    • changedInput schema / properties / path / description
      Previous value: -"e.g. /companies/{companyId}/tag-groups"New value: +"API path below /v1, e.g. /companies/{companyId}/tag-groups; query values go in params"
    • addedInput schema / properties / path / minLength
      Added value: +1
    • addedInput schema / properties / path / pattern
      Added value: +"^[\\w\\-/{}]*(?:\\.[\\w\\-/{}]+)*\\.?$"
  2. Addedv0.4.0

TDQS

A4/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, open-world operation. The description adds useful behavior detail: {companyId} substitution and that the response body is returned, but it does not cover error behavior, auth requirements, or pagination implications of arbitrary GET paths.

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 a single compact sentence that front-loads the main purpose and the key exclusion rule. It contains no filler and remains focused on what an agent needs to select the tool.

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?

Given the fully described schema, read-only/open-world annotations, and absence of an output schema, the description provides enough context to call the tool correctly. The remaining gaps, such as error handling and base-path details, are covered by the schema or outside what the description must carry here.

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%, so the path, params, and companyId semantics are already well documented in the schema. The description only adds the {companyId} substitution behavior, which is helpful but does not need to compensate for missing schema detail.

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 states a specific verb and resource: send a GET to any Bokio API path. It also distinguishes this tool from siblings by framing it as the escape hatch for paths that no other tool covers.

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 explicitly says to use this tool for paths no other tool covers, which gives clear guidance against reaching for it when a dedicated sibling exists. It does not enumerate specific alternatives, but the exclusion rule is stated directly.

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