Skip to main content
Glama

triple_extraction_options

Which ways of extracting triples work on this computer: "claude-code" (the user's Claude plan via the Claude Code command line), "codex" (the user's ChatGPT plan via the Codex command line), "anthropic" / "openai" (API keys in this…

Instructions

Which ways of extracting triples work on this computer: "claude-code" (the user's Claude plan via the Claude Code command line), "codex" (the user's ChatGPT plan via the Codex command line), "anthropic" / "openai" (API keys in this server's environment), and always "chat" (you extract them yourself with next_triple_batch and save_triples). Ask the user which to use.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.16.1

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that this is an environment-availability probe rather than an extraction, that some modes depend on the user's Claude/ChatGPT plans or server-side API keys, and that 'chat' is always available and requires the agent to extract manually via next_triple_batch and save_triples. It could add failure/fallback behavior when no backend is available, but the core behavior is disclosed.

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?

It is front-loaded with the core question ('which ways of extracting triples work on this computer') and the inline definitions of each mode earn their place. The sentence is long and elliptical in places ('and always "chat"...'), but there is no filler.

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?

For a zero-parameter capability-discovery tool with an output schema, the description covers what is returned, what each value means, and the mandatory next step of asking the user. The only omission is an explicit statement of when in the workflow to call it relative to extract_triples.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. The description appropriately spends its words on the meaning of the returned option names instead.

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 states a specific purpose: discovering which triple-extraction backends are available on this machine, and it names each candidate ('claude-code', 'codex', 'anthropic'/'openai', 'chat') with a one-line meaning. It is clearly not the same as extract_triples or next_triple_batch, though it never uses an explicit verb like 'list' or 'detect'.

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?

It gives actionable direction: check options, then 'Ask the user which to use', and it points to next_triple_batch and save_triples for the always-available 'chat' path. It stops short of an explicit 'call this before any extraction' or a when-not-to-use statement, so it falls just short of a 5.

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