Skip to main content
Glama
Sign In
mort-mcp

mort-mcp

by 0xmortuex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mort_examples

Lists bundled Mort example programs or displays a named example, helping agents learn syntax and idioms from known-good code.

Instructions

List the compiler's bundled example programs, or show one by name. Examples are known-good Mort - a fast way to learn idioms. Needs MORT_HOME.

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_examples"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/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 one genuinely useful operational fact: it requires MORT_HOME. It also vouches that examples are known-good. It does not say what happens when the name argument matches nothing, nor anything about output shape beyond what the output schema covers.

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 sentences with the listing mode front-loaded, the parameter-driven alternative second, and the environment prerequisite last. Nothing is redundant or padded.

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?

This is a simple one-parameter read tool with an output schema, so return values needn't be explained. The MORT_HOME requirement is the key environmental caveat and it is present; only the not-found/unmatched-name behavior is left unaddressed.

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 0% and the single optional `name` parameter is undocumented in the schema, but "or show one by name" does explain its role as a selector between list and single-item modes. It adds no detail on matching behavior (exact vs. partial, case sensitivity) or on valid names.

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 names a specific resource (the compiler's bundled example programs) and two concrete modes: list all, or show one by name. That is enough to distinguish it from siblings like mort_docs or mort_std without opening the schema, though it does not explicitly contrast itself against those doc-oriented siblings.

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?

"A fast way to learn idioms" implies the use case is learning by reading known-good code, which is real but indirect guidance. It states no exclusions and does not say when to prefer mort_docs or mort_std over this tool, so the agent must infer the boundary.

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