Skip to main content
Glama
dpdanpittman

mcp-server-quint

by dpdanpittman

quint_docs

Access a curated cheat sheet for Quint syntax and built-in operators. Get quick reference documentation for sets, maps, lists, actions, temporal logic, types, modules, or testing.

Instructions

Quick reference for Quint syntax and built-in operators. Returns a curated cheat sheet for the requested topic. No CLI call needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYesTopic: "sets", "maps", "lists", "actions", "temporal", "types", "modules", "testing", or "all" for the full reference

Implementation Reference

  • The handler for the 'quint_docs' tool, which provides a cheat sheet for Quint syntax and operators based on the requested topic.
    server.tool(
      "quint_docs",
      "Quick reference for Quint syntax and built-in operators. Returns a curated cheat sheet for the requested topic. No CLI call needed.",
      {
        topic: z
          .string()
          .describe(
            'Topic: "sets", "maps", "lists", "actions", "temporal", "types", "modules", "testing", or "all" for the full reference',
          ),
      },
      async ({ topic }) => {
        const topics = Object.keys(cheatsheet);
    
        if (topics.length === 0) {
          return {
            content: [
              {
                type: "text",
                text: "Error: cheatsheet reference data not found. Reinstall the server.",
              },
            ],
            isError: true,
          };
        }
    
        const key = topic.toLowerCase().trim();
    
        if (key === "all") {
          const sections = topics.map((t) => formatTopic(cheatsheet[t]));
          return { content: [{ type: "text", text: sections.join("\n\n") }] };
        }
    
        if (cheatsheet[key]) {
          return {
            content: [{ type: "text", text: formatTopic(cheatsheet[key]) }],
          };
        }
    
        return {
          content: [
            {
              type: "text",
              text: `Unknown topic "${topic}". Available topics: ${topics.join(", ")}, all`,
            },
          ],
          isError: true,
        };
      },
    );
  • Helper function used to format the documentation entries into a readable string for the 'quint_docs' tool.
    function formatTopic(section) {
      const lines = [`## ${section.title}`, section.description, ""];
      for (const entry of section.entries) {
        lines.push(`  ${entry.syntax}`);
        lines.push(`    \u2192 ${entry.description}`);
      }
      return lines.join("\n");
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the output ('Returns a curated cheat sheet') and operational aspect ('No CLI call needed'), but lacks details on response format, error handling, or performance characteristics like rate limits. It adds some value but not rich behavioral context.

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?

The description is two concise sentences with zero waste. The first sentence states the purpose and scope, and the second adds operational context, both earning their place. It's appropriately sized and front-loaded with key information.

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?

Given the tool's low complexity (single parameter, no output schema, no annotations), the description is mostly complete. It covers purpose, output type, and operational note. However, without an output schema, it could benefit from more detail on the cheat sheet format or example output to fully guide the agent.

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%, so the schema already documents the single 'topic' parameter with its allowed values. The description adds no additional parameter semantics beyond what the schema provides, such as examples or usage tips for specific topics. Baseline 3 is appropriate when schema does the heavy lifting.

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 description clearly states the tool's purpose with specific verbs ('Quick reference', 'Returns a curated cheat sheet') and resource ('Quint syntax and built-in operators'). It distinguishes from sibling tools like quint_run or quint_verify by focusing on documentation retrieval rather than code execution or verification.

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 provides clear context for when to use this tool ('Quick reference for Quint syntax and built-in operators') and implicitly contrasts with siblings by stating 'No CLI call needed', suggesting it's a lightweight alternative. However, it doesn't explicitly name when-not-to-use scenarios or direct alternatives among the siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dpdanpittman/mcp-server-quint'

If you have feedback or need assistance with the MCP directory API, please join our Discord server