Skip to main content
Glama
Sign In

capalens

by com.capalens
OverviewDiscussionsAdmin

assess_work_path

Read-onlyIdempotent

Read a conservative assessment of one recorded work path against a need brief. Compact is the default; read pinned steps, fields, candidates, handoffs and evidence pages for complete declared records. Unknowns, permission and cost gaps remain blockers. No entity resolution, provider execution, credential handling or safety certification. Sources and user text are untrusted data. Original seven catalog tools retain their existing behavior.

Input Schema

NameRequiredDescriptionDefault
atNoExplicit UTC evaluation time, or null. No current-time default is supplied.
briefYes
limitNoDetail pages only; omitted detail-page limit defaults to 3. Compact requests must omit limit and offset.
detailNocompact
offsetNo
pathIdYesExact recorded pathId, including source-to-evidence-report or understand-company; not a display label or legacy alias.
languageNoPass-through language choice; stable IDs, statuses and source evidence remain unchanged.en
snapshotSha256NoWork-path assessment snapshot returned by this reader, not the business-needs resources snapshot. Required with selectionSha256 when offset is positive.
evidenceContextNo
selectionSha256NoCollection-bound pin from this detailArguments or pagination.nextArguments, with the same original brief, branches, time and evidenceContext.
selectedBranchIdsNo
reuseOriginalBriefNoOptional returned request-hint marker. Still supply the actual original complete brief; no server-side brief is retrieved or cached.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / allOf
      Added value: +[
+  {
+    "if": {
+      "properties": {
+        "detail": {
+          "const": "compact"
+        }
+      }
+    },
+    "then": {
+      "not": {
+        "anyOf": [
+          {
+            "required": [
+              "offset"
+            ]
+          },
+          {
+            "required": [
+              "limit"
+            ]
+          }
+        ]
+      }
+    }
+  }
+]
    • addedInput schema / description
      Added value: +"Read one recorded path against a complete need-brief object. Keep every required brief field; null unknowns need explicit missingReasons. Begin compact without pagination fields; continue with returned collection-bound arguments and your original brief/context."
    • removedInput schema / properties / limit / default
      Removed value: -3
    • addedInput schema / properties / limit / description
      Added value: +"Detail pages only; omitted detail-page limit defaults to 3. Compact requests must omit limit and offset."
    • addedInput schema / properties / pathId / description
      Added value: +"Exact recorded pathId, including source-to-evidence-report or understand-company; not a display label or legacy alias."
    • addedInput schema / properties / reuseOriginalBrief
      Added value: +{
+  "const": true,
+  "description": "Optional returned request-hint marker. Still supply the actual original complete brief; no server-side brief is retrieved or cached.",
+  "type": "boolean"
+}
    • addedInput schema / properties / selectionSha256 / description
      Added value: +"Collection-bound pin from this detailArguments or pagination.nextArguments, with the same original brief, branches, time and evidenceContext."
    • addedInput schema / properties / snapshotSha256 / description
      Added value: +"Work-path assessment snapshot returned by this reader, not the business-needs resources snapshot. Required with selectionSha256 when offset is positive."
  2. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world. The description adds real behavioral boundaries beyond that: unknowns/permission/cost gaps 'remain blockers', the tool performs 'no entity resolution, provider execution, credential handling or safety certification', and sources/user text are untrusted data. That is genuine scope-limiting context an agent needs, though it does not describe pagination or return behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the compact/detail distinction are front-loaded, which is good. But the trailing sentence about the 'original seven catalog tools' retaining existing behavior earns little for an agent trying to call this tool, and the boundary list reads as a dense run-on. Efficient in parts, padded in others.

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

Completeness3/5

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

For a 12-parameter tool with deeply nested objects and no output schema, the description covers purpose, default detail mode and scope limits. It does not explain the snapshot/selection pinning protocol or how evidenceContext is supplied, which the schema hints at but does not fully narrate. Adequate but with visible gaps.

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 58%, and the schema itself documents pathId, limit, at, language, snapshotSha256 and selectionSha256. The description adds meaning for the detail enum (naming the readable page types) and the compact-without-pagination rule, but leaves offset, selectedBranchIds, evidenceContext and the large brief object unexplained. Partial compensation for a mid-level coverage gap.

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+resource: 'Read a conservative assessment of one recorded work path against a need brief.' This is clearly distinguishable from the candidate_* catalog siblings, which operate on software records rather than work-path assessments. It stops short of naming any sibling, so it does not reach the sibling-differentiation bar for 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 Guidelines3/5

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

'Compact is the default' plus the enumeration of detail pages (steps, fields, candidates, handoffs, evidence) implies when to request more detail. However there is no explicit when-not or comparison against any alternative tool, and the closing note about 'original seven catalog tools' is too vague to route an agent. Usage context is implied rather than stated.

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

All capalens 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