Marcora

learn_marcora_tools

Read-onlyIdempotent

Returns Marcora's guide to its own tools: what each Marcora object is, which tool fits which request, the order the tools chain in, and the mistakes to avoid.

When to use this tool: call it once before multi-step Marcora work the user has asked for — for example generating content into a project, setting a project brief, adding reference context, or producing a content plan — or whenever you are unsure which Marcora tool fits a request or how two of them chain. If the Marcora skill is already loaded in your context, you don't need this tool: it holds the same guidance.

Called with no topic, it returns an overview (the object model, the context model, a which-tool table) and the list of topics, each with a one-line summary. Call it again with topic for the one section the task needs; don't fetch every topic.

Read-only: it reads no workspace data, changes nothing, and uses no credits.

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

Input Schema

Name	Required	Description	Default
`topic`	No	Which section of the guide to return. Omit it for the overview, which lists every topic with a summary — then pass the topic whose summary matches the task (e.g. `projects-and-briefs` before working inside a project).

Output Schema

Name	Required	Description
`title`	Yes	Human-readable title of the section.
`topic`	Yes	The section returned: `overview`, or the topic that was requested.
`topics`	Yes	Every topic in the guide, in order. Pass one as `topic` to read that section.
`content`	Yes	The section's guidance, in markdown.
`guide_version`	Yes	Version of the Marcora guide this text comes from (matches the companion marcora-mcp skill's version).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world, so the bar is lower. The description still adds non-obvious behavioral facts absent from the annotations: it reads no workspace data, consumes no credits, and duplicates content already available via the Marcora skill — all relevant to whether an agent should call it at all.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then a bolded when-to-use block, then invocation mechanics, then a safety line — easy to scan. It is a little long relative to a single optional enum parameter, and the overview/topic mechanics partially restate the schema field description.

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?

An output schema exists, so return values need not be explained, and the description still tells the agent what the overview contains and how topics are surfaced. For a documentation tool with one optional parameter and full annotation coverage, nothing an agent needs to call it correctly is missing.

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 100% and the enum's own description already explains omit-for-overview versus pass-a-topic-with-a-matching-summary, so most parameter meaning is structured data. The description adds the operational constraint that only one topic should be fetched at a time, which shapes invocation rather than just naming the field.

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 first sentence names a specific verb and resource — returns Marcora's guide to its own tools — and enumerates the content: object model, which-tool mapping, chaining order, and pitfalls. Against ~55 CRUD/read siblings, this is unmistakably the meta-documentation tool rather than an action tool.

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

Usage Guidelines5/5

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

It gives an explicit when-to-use trigger (once before multi-step work: generating content, setting a brief, adding context, producing a plan) plus a fallback trigger (uncertainty about tool choice or chaining). It also names a when-not: if the Marcora skill is already loaded, this tool is redundant, and it prescribes a two-call strategy (overview first, then one topic) while warning against fetching every topic.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Marcora tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?