Skip to main content
Glama
kumarganduri

legwork-mcp

by kumarganduri
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

use_tool

Call an installed Legwork repo tool by repo and tool name when it isn't listed in your client; it runs in the granted sandbox and returns output or errors.

Instructions

Call a tool of a repo installed through Legwork, by repo and tool name. Most clients also list installed tools directly as __; use this when the tool isn't in your list yet. It runs in the sandbox with the folders and network granted at install. Replies with the tool's output, marked as untrusted text and size-capped, plus (on macOS) anything the sandbox blocked; files it makes are copied to ~/Legwork/outputs/ by default. Calling a repo that isn't installed is an error that says to call install_tool; a wrong tool name is an error listing the repo's tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoYesowner/repo of an installed tool, e.g. 'jsvine/pdfplumber'
toolYesthe tool's name as listed by install_tool or list_installed_tools, e.g. 'extract_tables'
argumentsNothe arguments for that tool, an object of its parameters, e.g. {'path': '~/Downloads/report.pdf'}. Paths may start with ~/. Omitted: no arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • addedInput schema / properties / arguments / description
      Added value: +"the arguments for that tool, an object of its parameters, e.g. {'path': '~/Downloads/report.pdf'}. Paths may start with ~/. Omitted: no arguments"
    • addedInput schema / properties / repo / description
      Added value: +"owner/repo of an installed tool, e.g. 'jsvine/pdfplumber'"
    • addedInput schema / properties / tool / description
      Added value: +"the tool's name as listed by install_tool or list_installed_tools, e.g. 'extract_tables'"
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=false, destructiveHint=false) by disclosing the execution sandbox and its granted folders/network, that output is marked untrusted and size-capped, that macOS reports sandbox blocks, and that produced files land in ~/Legwork/outputs/ by default. Both failure modes are described with their recovery paths.

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?

Purpose is front-loaded and every clause carries information (usage routing, sandbox, output handling, error behavior) with no filler. The semicolon-chained sentences are dense and slightly hard to scan, which keeps it short of a 5.

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?

For a 3-parameter dispatch tool with no output schema, the description covers invocation addressing, execution environment, return-value handling (untrusted marking, size cap, output file location), and both error cases. 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so repo, tool, and arguments are already documented, including the owner/repo format and examples. The description reinforces the repo+tool addressing model but adds no syntax or constraints beyond what the schema states, so the baseline 3 applies.

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+resource ('Call a tool of a repo installed through Legwork, by repo and tool name') and immediately distinguishes itself from the sibling tools by explaining that most clients list installed tools directly as <repo>__<tool>. An agent can tell this apart from install_tool or list_installed_tools without opening 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 Guidelines5/5

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

Explicitly names the alternative surface ('most clients also list installed tools directly as <repo>__<tool>') and the selecting condition ('use this when the tool isn't in your list yet'). It also gives error-routing guidance: an uninstalled repo errors telling you to call install_tool, and a bad tool name errors with a list of the repo's tools.

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