Manulyx: LaTeX editor

List my Manulyx projects

list_projects

Read-only

Lists the Manulyx projects you can open (yours and those shared with you), with their ids, your role, main file and last compile status. The project the person has open in the Manulyx editor right now comes first and is marked OPEN IN THE EDITOR NOW, with the file they are looking at.

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

Input Schema

Name	Required	Description	Default
`search`	No	Optional words to find in the title.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds genuinely new behavior: what fields are returned (ids, role, main file, compile status) and a deterministic ordering rule that puts the currently-open project first with a marker. It omits anything about list size limits or how many projects can be returned, which is a modest gap for a listing tool.

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?

Two sentences, no filler, and the returned-field list is packed into the first sentence before the ordering rule. The second sentence is somewhat long and the editorial-capitalized marker is slightly awkward to parse, but nothing is redundant.

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?

With no output schema, the description must explain return values, and it does so concretely: ids, role, main file, last compile status, plus the sort order and the editor-open marker. For a single-optional-parameter read tool with annotations covering safety, nothing an agent needs in order to call or interpret it is missing.

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 100% for the single optional 'search' parameter, so the schema fully carries parameter meaning. The description never mentions filtering at all, adding nothing beyond the structured field, which lands exactly at the baseline.

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 opens with a specific verb and resource ('Lists the Manulyx projects') and defines the scope as 'yours and those shared with you', which separates it from a broad search like search_all_projects. It stops short of naming that sibling explicitly, so the differentiation is inferred from scope rather than stated.

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 only implied: an agent can infer this is the browsing/listing entry point, but there is no explicit 'use this when' statement, no exclusion, and no pointer to search_all_projects or compile for follow-up actions. The 'open in the editor now' note hints at a discovery use case but doesn't articulate it as guidance.

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

All Manulyx: LaTeX editor tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?