Skip to main content
Glama
stockbit-mcp

stockbit-mcp

Broker list

broker_list
Read-onlyIdempotent

Translate Stockbit broker codes like YP, CC, or AK into broker names, types, and groups using the broker directory endpoint.

Instructions

All broker codes with their names and type, to translate codes such as YP, CC or AK.

Returns (Stockbit's data field): data[{id, code, name, permission, group 'Lokal'|'Asing'|'Pemerintah', color, membership_type MEMBERSHIP_TYPE_EXCHANGE_MEMBER}] (112 rows).

Endpoint: GET exodus /findata-view/marketdetectors/brokers.

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": "broker_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNopage Default 1.
groupNoOther group values unknown. Default "GROUP_UNSPECIFIED".
limitNolimit Default 150.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered; the description adds real value beyond that with the exact return field list, the group domain 'Lokal'|'Asing'|'Pemerintah', the total row count (112 rows), and the underlying endpoint. It stops short of describing pagination behavior explicitly, leaving the agent to infer from 112 rows vs the default limit of 150.

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 purpose and use case are front-loaded in the first sentence, with return shape and endpoint after. The '(Stockbit's data field)' framing and raw pseudo-JSON are terse internal jargon, but each element is information an agent can use.

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 read-only reference list with no output schema, the description compensates well by enumerating the returned fields and row count, and by naming the endpoint. The one gap is that it doesn't state how the unknown 'group' enum values interact with the 'Lokal'|'Asing'|'Pemerintah' domain shown in the return payload.

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 page, group and limit are already documented including their defaults; the description adds no field-level meaning for those parameters beyond the implicit note that the full set is 112 rows. Baseline 3 applies when the schema carries the parameter burden.

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 resource ('All broker codes with their names and type') and adds the concrete job it performs ('to translate codes such as YP, CC or AK'), which distinguishes it from the broker_activity/broker_summary siblings that report trading behavior rather than a reference dictionary.

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?

The translation use case ('to translate codes such as YP, CC or AK') gives a clear condition for reaching for this tool rather than other broker_* tools, but it names no explicit alternative and gives no when-not guidance, so an agent still infers selection from context.

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