tools

A set of coding rules for adding MCP tools to a software project. It covers how tools are created, described, connected to permissions, and registered.

In plain words
What is it for?
Use it when building or reviewing MCP tools, including their factory functions, callbacks, names, groups, descriptions, and access scopes.
Why use it?
It reduces the chance that a new tool is wired into the project inconsistently or left out of a required registry or permission list.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/tableau/tableau-mcp/tools
Clone the repo
git clone --depth 1 https://github.com/tableau/tableau-mcp

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 889 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00889
Opus 5 $0.00000 $0.00445
Sonnet 5 $0.00000 $0.00178
Haiku 4.5 $0.00000 $0.00089

Measured yesterday against content hash d51439a427b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

tools scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

3 near-identical copies found in the catalogue:

  • tools — 100% identical, 0 lines differ
  • tools — 100% identical, 0 lines differ
  • tools — 97% identical, 2 lines differ
.cursor/rules/tools.mdc · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Tool Development Patterns

Factory Pattern

Every tool exports a factory function registered in src/tools/tools.ts:

export const getMyTool = (server: Server): Tool<typeof paramsSchema> => {
  const myTool = new Tool({
    server,
    name: 'my-tool',           // Must be in ToolName union (src/tools/toolName.ts)
    description: '...',
    paramsSchema,               // Zod schema object (not z.object, just raw shape)
    annotations: { title: 'My Tool', readOnlyHint: true, openWorldHint: false },
    callback: async (args, extra) => { ... },
  });
  return myTool;
};

Adding a New Tool — Checklist

  1. Add tool name to toolNames array in src/tools/toolName.ts
  2. Add to appropriate toolGroups entry (or create new group)
  3. Add scope mapping in src/server/oauth/scopes.ts (toolScopeMap)
  4. Create tool directory under src/tools/
  5. Implement factory function following the pattern above
  6. Register factory in src/tools/tools.ts (toolFactories array)

Tool Callback Pattern

Callbacks use logAndExecute from the base Tool class:

callback: async (args, extra): Promise<CallToolResult> => {
  return await myTool.logAndExecute({
    extra,
    args,
    callback: async () => {
      const result = await useRestApi({
        ...extra,
        jwtScopes: myTool.requiredApiScopes,
        callback: async (restApi) => {
          // Use restApi methods here
          return data;
        },
      });
      return new Ok(result);     // ts-results-es Ok()
    },
    constrainSuccessResult: (result) => constrainMyResult(result),
  });
},

Result Types

  • Result<T, E> from ts-results-es — tool callbacks return this
  • Ok(value) for success, Err(error) for typed errors
  • ConstrainedResult<T> — post-processing step with three outcomes:
    • { type: 'success', result: T } — data returned to client
    • { type: 'empty', message: string } — no data found (not an error)
    • { type: 'error', message: string, error?: Error } — logical error

Read the full file on GitHub · 98 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 98 lines · 0 tokens per session scan A d51439a427b8

Subscribe to this mod's changes

tools is a cursor rule published in the GitHub repository tableau/tableau-mcp (329 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 889 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other cursor rules, from other repositories

thing

Cursor rule "thing" from burugo/one-mcp, covering rule name: thing orm usage guide, description, core concept, configuration and basic usage.

burugo/one-mcp · 0 tokens

tdd

Final Verification: Always use: go test -v ./backend/api/handler/... | grep FAIL.

burugo/one-mcp · 0 tokens

language

Always respond in Chinese with utf-8 encoding. Git commit messages and code comments should always be in English. Remember, programs must be written for people to read, and only incidentally for machines to execute.

burugo/one-mcp · 56 tokens

mcp-framework

We are in the mcp-framework , a typescript framework that allows construction of model context protocol (mcp) servers. We are implementing the new specification: Overview MCP provides a standardized way for applications to.

QuantGeekDev/mcp-framework · 0 tokens

elysia

TITLE: Elysia Supported Schema Validation Types DESCRIPTION: Elysia provides declarative schema support for various parts of an HTTP request and response, enabling robust validation and automatic OpenAPI generation. SOURCE: https://github.com/elysiajs/documentation/blob/main/docs/essential/validation.md#snippet3.

kerlos/elysia-mcp · 0 tokens

mcp

TITLE: Implement Transport Error Handling in TypeScript and Python DESCRIPTION: This code snippet illustrates how to incorporate comprehensive error handling within transport implementations. It demonstrates catching exceptions during connection establishment and message transmission, logging errors, and ensuring…

kerlos/elysia-mcp · 0 tokens