obs_public_list_branchesList published course branch codes (e.g., BLG, YZV, MAT) for a program level without logging in. Use it to discover available branches for a given level.
List every course branch code (BLG, YZV, MAT, ...) published for a program level. No login required.
| Name | Required | Description | Default |
|---|---|---|---|
| level | No | LS |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full disclosure burden, and it usefully states 'No login required,' which is a behavioral fact beyond the schema. The phrasing 'List' and 'published' also implies a read-only, public operation, though side effects and error behavior are not explicitly discussed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences deliver the core purpose, scope, examples, and auth requirement with no filler. The key action and scope appear first, making the definition easy to scan.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple and the output schema covers return values, so the description does not need to explain those. However, the missing explanation of valid program-level values and the lack of any sibling routing leaves a noticeable gap for correct invocation beyond the default.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and the description only loosely maps the 'level' parameter to 'program level,' without explaining allowed values or what the default 'LS' means. Because the schema provides no enum or property description, the description needed to compensate more and does not.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb-object pair ('List every course branch code') and gives concrete examples (BLG, YZV, MAT) plus a scope qualifier ('published for a program level'). It is easily distinguishable from sibling tools such as obs_public_list_plans and list_courses.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly scopes the operation to retrieving branch codes for a program level and states that no login is required, which signals when to use it over authentication-gated siblings. It does not explicitly name alternatives or exclusion cases, but the intended context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.