Skip to main content
Glama
macula-io

Macula MCP

by macula-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

mesh_get

Fetch a content-addressed artifact by its 100-character MCID from any node sharing it. Every byte is checked against the MCID, and content is returned as base64.

Instructions

Fetch a content-addressed artifact by its MCID (100 hex characters, as mesh_put returns it) from any node that shares it; every byte is checked against the MCID, so no sharer is trusted. Returns the content as base64. code=not_shared means no node shares it right now.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mcid_hexYesThe artifact's MCID, as mesh_put returned it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.37.0
    • removedInput schema / properties / host
      Removed value: -{
-  "description": "Station to connect through, \"host[:port]\". Defaults to station-de-frankfurt.macula.io:4433.",
-  "type": "string"
-}
    • changedInput schema / properties / mcid_hex / description
      Previous value: -"MCID returned by mesh_put."New value: +"The artifact's MCID, as mesh_put returned it."
    • changedInput schema / properties / mcid_hex / maxLength
      Previous value: -68New value: +100
    • changedInput schema / properties / mcid_hex / minLength
      Previous value: -68New value: +100
  2. First observedv0.28.7

TDQS

A4.3/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 well: it discloses that bytes are verified against the MCID so no sharer is trusted, that the payload is returned as base64, and that code=not_shared signals no current sharer. It omits permission/auth requirements and any timeout or size limits.

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 tightly packed sentences, front-loaded with the action and resource, followed by the trust/return contract and the failure code. No filler.

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

Completeness5/5

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

There is no output schema, so the description must explain return values — it does (base64 content, code=not_shared). For a single-parameter read tool this covers what an agent needs to call it and interpret the result.

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 coverage is 100% and the single parameter is fully documented (pattern, exact 100-char length). The description's '100 hex characters' and 'as mesh_put returns it' largely restate the schema, adding only a minor cross-tool provenance cue, so the baseline 3 is correct.

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?

States a specific verb (Fetch) and resource (content-addressed artifact) plus the key scope constraint (from any node that shares it). It also anchors the input to a sibling ('as mesh_put returns it'), so an agent can distinguish this retrieval tool from the put/find family without reading any schema.

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 description makes the usage context clear: fetch an artifact whose MCID you already hold from a prior mesh_put. It does not state when *not* to use it or name any competing alternative explicitly, so it stops short of the top score.

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