Skip to main content
Glama
Sign In
mort-mcp

mort-mcp

by 0xmortuex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mort_std

Lists Mort standard library modules or shows a module's public functions, structs and enums with exact signatures and doc comments, read from the installed compiler's source.

Instructions

Look up the standard library.

With no module: list every std module. With a module (e.g. "strings" or "std.vec"): its public functions, structs and enums with exact signatures and doc comments, read from the installed compiler's source.

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

Input Schema

NameRequiredDescriptionDefault
moduleNo

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

With no annotations, the description carries the full burden and does disclose meaningful behavior: results are "read from the installed compiler's source," which tells the agent the answer is version-specific and authoritative rather than cached online docs. It omits failure behavior for a non-existent module name, which is the main residual gap for a no-annotation tool.

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?

Two short blocks, front-loaded with the core action, followed immediately by the mode split. Every sentence carries information an agent needs and nothing is redundant.

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 one-optional-parameter lookup with an output schema already defined, the description covers both modes, the content returned (signatures and doc comments), and the data source. Only the unknown-module case is unaddressed, a minor omission given the low complexity.

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?

Schema coverage is 0%, so the description must compensate and does: it explains that the single parameter is optional, what omission means (list every module), and what a value means. The examples "strings" and "std.vec" additionally convey the accepted naming forms (bare name or std-prefixed), which the bare {"type":"string"} schema does not.

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 gives a specific verb and resource ("Look up the standard library") plus the two result shapes it can produce: a module list or per-module symbols. It is clear enough to distinguish from most siblings, but it never remarks on the nearby mort_docs tool, so an agent must infer that one is stdlib-only and the other is presumably general documentation.

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 two calling modes are spelled out explicitly: omit the module to enumerate all std modules, pass one to get its public API. That is clear selection guidance for the tool's own parameter, but there is no exclusion clause pointing to an alternative sibling when the agent actually wants general project docs rather than stdlib.

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