capalens

get_software

Read-onlyIdempotent

Read software details, provenance, sources and documentation review scope. Optional fields:["businessNeeds"] returns documented industry/business-task mappings with evidence and limits; unmapped does not mean unsupported. It can be combined with selectionGuide and pricingV2, except pricingPart sections. Optional fields:["selectionGuide"] provides an explicit compact human-review view; it can be combined with pricingV2. Optional pricing-0.4.2: fields:["pricingV2"] returns only the scoped pricing view; pricing:"detail" requires one interfaceId. For large details use pricingPart:"overview", then pinned rules/sources pages: exactly fields:["pricingV2"], pricing:"detail", interfaceId. Each pricingOffset returns one whole section item. Offset>0 requires pricingSnapshotSha256 from overview; follow sectionArguments/nextArguments. All sections from one snapshot are required; no page alone is a complete quote. Four fee layers, unknown values and source scopes remain separate; prices are partial source observations, not a total bill. No live availability or safety certification. Listed vendor MCP/API/CLI integrations are untested; docs-reviewed means documentation review only. Results include vendorTestingPolicy; CapaLens protocol tests do not test or certify vendors.

Input Schema

Name	Required	Description	Default
`id`	Yes
`fields`	No
`pricing`	No
`language`	No	Output language, including vendorTesting labels and vendorTestingPolicy. English is the default; IDs, URLs, documentation verification values and commands are unchanged. Vendor integrations remain untested in both languages.	en
`interfaceId`	No
`pricingPart`	No	Lossless section; requires pricing: detail, interfaceId and exactly fields: [pricingV2]. Read overview and every pinned rules/sources page.
`pricingOffset`	No	Only with pricingPart. One complete item per page; overview only 0. Offset>0 requires pricingSnapshotSha256.
`pricingSnapshotSha256`	No	Optional snapshot consistency pin at offset0; required above0. Must equal original metadata.sidecarSha256. This is not authentication or a quota identity.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 18, 2026

changedInput schema / properties / fields / items / enum

Previous value: -[
-  "pricingV2",
-  "selectionGuide"
-]New value: +[
+  "pricingV2",
+  "selectionGuide",
+  "businessNeeds"
+]

changedInput schema / properties / fields / maxItems
```
Previous value: -2New value: +3
```

Changed7 schema fields changedOct 18, 2026

addedInput schema / allOf

Added value: +[
+  {
+    "else": {
+      "not": {
+        "anyOf": [
+          {
+            "required": [
+              "pricingOffset"
+            ]
+          },
+          {
+            "required": [
+              "pricingSnapshotSha256"
+            ]
+          }
+        ]
+      }
+    },
+    "if": {
+      "required": [
+        "pricingPart"
+      ]
+    },
+    "then": {
+      "properties": {
+        "fields": {
+          "const": [
+            "pricingV2"
+          ]
+        },
+        "pricing": {
+          "const": "detail"
+        }
+      },
+      "required": [
+        "pricing",
+        "interfaceId",
+        "fields"
+      ]
+    }
+  },
+  {
+    "if": {
+      "properties": {
+        "pricingPart": {
+          "const": "overview"
+        }
+      },
+      "required": [
+        "pricingPart"
+      ]
+    },
+    "then": {
+      "properties": {
+        "pricingOffset": {
+          "const": 0
+        }
+      }
+    }
+  },
+  {
+    "if": {
+      "properties": {
+        "pricingOffset": {
+          "minimum": 1
+        }
+      },
+      "required": [
+        "pricingOffset"
+      ]
+    },
+    "then": {
+      "required": [
+        "pricingSnapshotSha256"
+      ]
+    }
+  }
+]

addedInput schema / properties / fields

Added value: +{
+  "items": {
+    "enum": [
+      "pricingV2",
+      "selectionGuide"
+    ],
+    "type": "string"
+  },
+  "maxItems": 2,
+  "minItems": 1,
+  "type": "array",
+  "uniqueItems": true
+}

addedInput schema / properties / interfaceId

Added value: +{
+  "maxLength": 120,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / pricing

Added value: +{
+  "enum": [
+    "summary",
+    "detail"
+  ],
+  "type": "string"
+}

addedInput schema / properties / pricingOffset

Added value: +{
+  "default": 0,
+  "description": "Only with pricingPart. One complete item per page; overview only 0. Offset>0 requires pricingSnapshotSha256.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / pricingPart

Added value: +{
+  "description": "Lossless section; requires pricing: detail, interfaceId and exactly fields: [pricingV2]. Read overview and every pinned rules/sources page.",
+  "enum": [
+    "overview",
+    "rules",
+    "sources"
+  ],
+  "type": "string"
+}

addedInput schema / properties / pricingSnapshotSha256

Added value: +{
+  "description": "Optional snapshot consistency pin at offset0; required above0. Must equal original metadata.sidecarSha256. This is not authentication or a quota identity.",
+  "maxLength": 64,
+  "minLength": 64,
+  "pattern": "^[a-f0-9]{64}$",
+  "type": "string"
+}

First observedOct 17, 2026

TDQS

A3.7/5.0

Behavior5/5

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

Annotations only cover safety (readOnly/idempotent/non-destructive). The description goes well beyond: it warns that vendor integrations are untested, that 'docs-reviewed' means documentation review only, that prices are partial source observations rather than a total bill, and that no live availability or safety certification exists. These caveats materially change how an agent should interpret results.

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

Conciseness2/5

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

Front-loads the purpose correctly, but the body is a dense run-on blob with malformed fragments like 'Optional fields:["businessNeeds"] returns...' and 'Optional pricing-0.4.2:'. Heavy pagination minutiae is packed into the top-level description rather than being deferred, hurting scannability without adding selection value.

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 an 8-param tool with no output schema, the description does explain the pricing sub-flow and several field returns, but it never describes the overall returned shape or the base (non-optional-field) result, and the vendorTestingPolicy reference is mentioned without saying what it contains. Adequate for invocation, thin for interpreting output.

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?

With only 50% schema description coverage across 8 params, the description carries real load: it explains what businessNeeds, selectionGuide and pricingV2 return, the pricing:'detail' + interfaceId + fields requirement, the overview→rules/sources pagination flow, and the pricingSnapshotSha256 consistency pin. It adds interaction semantics the JSON schema's allOf can only imply structurally.

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?

Opens with a concrete verb+resource: 'Read software details, provenance, sources and documentation review scope.' An agent immediately knows this is the detail-fetch tool. However, it never distinguishes itself from siblings like search_software, compare_software, or get_review_summary, so an agent must infer the boundary.

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?

Provides real combinatorial guidance ('can be combined with selectionGuide and pricingV2, except pricingPart sections') and a multi-step workflow for large pricing details. But it gives no guidance on when to choose this tool over its siblings (e.g., when to search vs. fetch detail), which is the core when-to-use question.

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

All capalens tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?