Skip to main content
Glama
Sign In

Hokmah

by io.github.davidangularme
OverviewDiscussionsAdmin

Compare Feature Zones

hokmah_compare
Read-onlyIdempotent

Ranks 2 to 8 zones of an imported repository from the one that works worst to the one that works best, with the reasons: fixes per feature, fixes per 1000 lines and tests, over the last 12 months. Each zone is a path prefix or a few words.

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": {
      "repo_url": "<repo_url>",
      "zones": "<zones>"
    },
    "name": "hokmah_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
zonesYes
repo_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description earns credit for adding substance: the 2–8 zone bound, the 12-month window, and the specific metrics used for ranking. It does not say what happens if the repository was never imported, which is the main behavioral gap.

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?

Two dense sentences that front-load the core action and the ranking direction, with no filler. The metric clause ("fixes per 1000 lines and tests") is slightly compressed and reads as a three-item list where the boundaries blur.

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?

An output schema exists, so the return shape need not be explained, and the description covers the ranking semantics and input constraints that remain. The missing pieces — whether repo_url must be a previously imported repo and what happens on invalid zone counts — are minor but real for a two-required-parameter tool.

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 coverage is 0%, so the description carries the burden; it partially compensates by defining a zone as "a path prefix or a few words" and by bounding the array to 2–8 entries, neither of which is in the schema. However, repo_url gets no treatment at all beyond the word "imported" — no format or prerequisite is stated.

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?

States a specific verb and resource ("ranks 2 to 8 zones of an imported repository") plus the ranking direction (worst to best) and the metric basis. An agent can tell this is a multi-zone comparison rather than a single-zone check, but it never names hokmah_zone_health or hokmah_overview to make that distinction explicit.

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

Usage Guidelines3/5

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

Usage is implied by the constraint "2 to 8 zones" and by "imported repository," which hints the repo must already be connected. There is no explicit when-to-use versus hokmah_zone_health (single zone) or hokmah_overview, and no stated fallback when fewer than two zones are relevant.

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

All Hokmah toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources