Skip to main content
Glama

ProvenPin

by io.github.provenpin
OverviewDiscussionsAdmin

Search tested recipes

search_recipes
Read-only

Find a tested, version-pinned code recipe for wiring libraries together. Call this BEFORE writing glue code that combines 2+ libraries (auth + framework, ORM + database, payments webhooks, queues, validation, request mocking, logging), and when you hit version conflicts, peer-dependency errors, or integration errors between libraries. Example queries: 'express stripe webhook', 'fastapi sqlmodel crud', 'hono jwt'. Only recipes whose latest test run passed are returned. Each result lists its exact pinned versions and a test receipt (receipt.last_passed_at). Pass the project's lockfile or a {package: version} map as versions: recipes that match the installed versions rank first and each result gets a compatibility summary. If nothing matches, write the code yourself; try list_stacks to see what is covered.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYesWhat you are wiring together, in plain words or library names, e.g. 'django rest api' or 'rq redis jobs'.
stackNoOnly recipes that use all of these libraries.
languageNo
versionsNoOptional but recommended: the versions in the user's project, so results are checked against them. Either a map like {"next": "15.2.0", "zod": "3.23.8"} or the raw text of package.json, package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock or uv.lock (max 200KB). Used only for this call, never stored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / versions
      Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "Optional but recommended: the versions in the user's project, so results are checked against them. Either a map like {\"next\": \"15.2.0\", \"zod\": \"3.23.8\"} or the raw text of package.json, package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock or uv.lock (max 200KB). Used only for this call, never stored.",
+  "type": [
+    "object",
+    "string"
+  ]
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only cover read-only and closed-world, so the description carries most of the burden and does: results are filtered to latest-test-passed, each carries pinned versions and receipt.last_passed_at, versions are used only for the call and never stored. It stops short of stating pagination or ranking limits beyond 'rank first'.

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?

Front-loaded with the core action and usage trigger, then examples, then result semantics and fallback. Dense but every clause serves a purpose; the parenthetical library-pair list is long though it directly helps query construction.

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?

No output schema, so the description correctly explains the return shape (pinned versions, test receipt, compatibility summary), result filtering, and the fallback path. It omits pagination behavior and whether empty-result calls have side effects, but overall an agent has what it needs to call this safely and correctly.

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?

Schema description coverage is 60%, so the description must compensate for the uncovered params (limit, language, stack): it explains that versions accepts a lockfile or a {package: version} map and that matching installed versions rank first with a compatibility summary. limit, language, and stack are left entirely to the schema, which is a visible gap but not a fatal one.

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?

Specific verb and resource ('find a tested, version-pinned code recipe for wiring libraries together') that sharply distinguishes it from sibling get_recipe (singular retrieval) and list_stacks (coverage browsing). It also names when to invoke it, before writing glue code, which no sibling claims.

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?

Explicit triggering conditions ('BEFORE writing glue code that combines 2+ libraries', 'when you hit version conflicts, peer-dependency errors, or integration errors'), example queries supplied, and a fallback rule ('If nothing matches, write the code yourself; try list_stacks'). This is close to exhaustive routing guidance.

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

All ProvenPin toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources