Skip to main content
Glama

Start here

commercebook_start_read
Read-onlyIdempotent

Start here: call it first in a new conversation. It reads the briefing for your role (buyer, seller or warehouse), which says what to do on CommerceBook, in order, and the rules. With a key it also reads who the key belongs to, your member and the key’s standing. It changes nothing. Actions (the activity each needs):

  • briefing (no key): the briefing for a role (role buyer, seller or warehouse): what to do here and the rules.

  • whoami (needs a key): who the key belongs to, with the API base and the key prefix.

  • me (needs a key): your member, its company, verification and counts.

  • standing (needs a key): your strikes and whether you may post.

  • openapi (needs a key): the OpenAPI document of the API. Send action and its arguments. Without action it runs briefing. With a key, or with ?role=buyer, seller, warehouse or all, the server also lists the separate tools that list, order, pay and ship.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "commercebook_start_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoFor briefing. The briefing to return: buyer, seller or warehouse. Left out: buyer without a key, the key’s own kind with a key.
actionNoThe action to run (briefing when left out).briefing

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so "It changes nothing" is largely redundant. The description does add real behavioral context beyond annotations: per-action key requirements and the non-obvious side effect that the server also lists separate list/order/pay/ship tools when a key or ?role is supplied.

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?

Front-loaded with the key instruction and then a scannable bullet per action, which suits a five-action dispatcher. Minor waste: "It changes nothing" restates annotations, and the final sentence about extra listed tools is dense and slightly hard to parse.

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?

With no output schema, the description correctly carries the burden of saying what each action returns, which it does. One gap: it mentions `?role=all` as an option while the schema enum only permits buyer, seller and warehouse, leaving the agent unsure whether `all` is a valid argument.

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?

The schema covers both parameters at 100% with enums and defaults, so the baseline is 3, but the action list adds meaning the enum values don't carry — what whoami returns (API base, key prefix), what me returns (company, verification, counts), and what standing returns (strikes, posting permission). The role defaulting rule is repeated from the schema rather than extended.

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 instruction ("call it first in a new conversation") and a concrete verb+resource ("reads the briefing for your role"), then enumerates all five actions with what each returns. An agent can distinguish this entry-point/dispatcher from tools like commercebook_market or commercebook_tool_search without inspecting the schema.

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 explicit when-to-use guidance ("call it first in a new conversation") and states defaults for both the action and role parameters in two contexts. It does not address when *not* to use it or name a sibling alternative, which keeps it out of 5 territory.

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.