Skip to main content
Glama

Recipe ingredient metadata

bpj_recipe_ingredient_metadata
Read-onlyIdempotent

Build a Recipe from line-separated ingredients and directions with prep time in minutes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "ingredients": "<ingredients>",
      "steps": "<steps>",
      "minutes": "<minutes>"
    },
    "name": "bpj_recipe_ingredient_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
stepsYes
minutesYes
ingredientsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, lowering the bar. The description contributes the input convention (line-separated text, minutes as the time unit), but for a tool whose verb is "Build" it never says what is produced — schema.org Recipe markup, JSON, or plain text — which is the main behavioral unknown here.

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?

A single front-loaded sentence with no filler; the input-format details are packed in efficiently. It is perhaps too terse rather than padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Four required parameters, no output schema, and no annotation detail about the return means the description should say what the built Recipe looks like. It doesn't, so an agent cannot predict the result shape before calling.

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 0%, so the description must carry the meaning. It does account for all four inputs (name, ingredients, steps, minutes) and clarifies the line-separated convention and minutes unit, but omits the size and range constraints (maxLength 240/3000, 1–10080) that also gate correct calls.

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?

"Build a Recipe" states a specific verb and resource, and the description adds the key detail that ingredients and directions arrive as line-separated text with prep time in minutes. It does not differentiate from the many sibling ..._metadata tools, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use statement, no exclusion, and no named alternative among the very large sibling catalog. An agent must infer from the name that this is the recipe-flavored member of the metadata family.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.