Skip to main content
Glama

List stdlib modules

stdlib_modules
Read-onlyIdempotent

List stdlib modules available in this AILANG version with one-line summaries.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "forVersion": "<forVersion>"
    },
    "name": "stdlib_modules"
  }
}

Input Schema

NameRequiredDescriptionDefault
forVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare this as read-only, idempotent, closed-world, and non-destructive, so the safety profile is covered. The description adds that results are version-scoped and include one-line summaries, but it does not mention pagination, result ordering, or how missing/invalid versions are handled.

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 definition is a single front-loaded sentence with no filler. The purpose, version scope, and summary content are all conveyed efficiently.

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 simple read-only list tool with one required parameter and no output schema, the description is adequate but thin. The main missing piece is parameter guidance for the version string, which is especially important given 0% schema description coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden for explaining forVersion. It clarifies that the parameter selects an AILANG version, but it does not specify the expected version format, whether partial versions are accepted, or what happens with an unknown version.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: 'List stdlib modules', scoped to 'this AILANG version', and notes that results include one-line summaries. It implicitly distinguishes itself from detail-oriented siblings like stdlib_module and stdlib_search, but does not name an alternative explicitly.

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

Usage Guidelines3/5

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

Usage is implied: an agent should call this when it needs an overview of available stdlib modules for a particular AILANG version. There is no explicit when-to-use or when-not-to-use guidance and no named alternative for looking up a single module or searching by keyword.

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.