Skip to main content
Glama
Sign In
bsp-mcp

bsp-mcp

Official
by Biological-Sovereignty-Protocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bsp_list_beos

Retrieves a paginated list of biological entity objects (BEOs) accessible under your configured IEO, with optional limits and offsets.

Instructions

List BEOs accessible to the configured IEO

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of BEOs to return (default: 20, max: 100).
offsetNoNumber of records to skip for pagination (default: 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description must carry the full behavioral burden. It only implies a read-only operation via 'List' but does not disclose pagination behavior, error cases, ordering, or response structure. It fails to add meaningful operational details beyond the schema.

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 sentence with no fluff or redundancy. It is appropriately sized for a simple list operation and front-loads the core purpose immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a straightforward list tool, the description covers the core purpose. However, with no output schema, it does not hint at the return format or any caveats (e.g., only unlocked BEOs). The lack of usage context and behavioral details leaves the agent with some ambiguity, but the simplicity keeps it at a passable level.

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?

The input schema provides 100% coverage, with both 'limit' and 'offset' having descriptive text. The description adds no parameter-specific meaning, but the schema does the heavy lifting, so a baseline of 3 is appropriate.

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 clearly states the verb 'List', the resource 'BEOs', and the scope 'accessible to the configured IEO'. This distinguishes it from sibling tools like bsp_destroy_beo or bsp_lock_beo, which target different operations on BEOs.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus siblings such as bsp_get_beo_summary or bsp_list_ieos. There are no conditions, exclusions, or contextual hints beyond the bare purpose, leaving the agent to infer usage from the name alone.

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