Cloche

Company definitions

company_metrics_and_definitions

Read-only

Returns this organization's own definitions of its metrics, terms and rules, and its verified queries: KPIs, revenue, players, customers, churn, retention, segments, and how to count them. With no input, the index of every definition. With query, matching definitions. With paths, the files.

Input Schema

Name	Required	Description
`paths`	No	files by their path in the index, or a folder ending in / for its files and folders, the root being /
`query`	No	words to find in the definitions
`since`	No	a change id, such as an earlier answer's head: returns the changes after it
`organization`	No	an organization id, for a person in several organizations that keep definitions

Output Schema

Name	Required	Description	Default
`head`	No
`note`	No
`files`	No
`total`	No
`readme`	No
`changes`	No
`covered`	No
`entries`	No
`folders`	No
`matches`	No
`missing`	No
`truncated`	Yes
`organization_id`	Yes
`organization_name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 18, 2026
- addedOutput schema / properties / entries / items / properties / last_changed_by_name
```
Added value: +{
+  "type": [
+    "null",
+    "string"
+  ]
+}
```
- addedOutput schema / properties / files / items / properties / last_changed_by_name
```
Added value: +{
+  "type": [
+    "null",
+    "string"
+  ]
+}
```
AddedOct 17, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by disclosing that behavior changes with input (index vs. matching definitions vs. files), which is not evident from the schema alone. Pagination/change semantics are left implicit.

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?

Three tight sentences, front-loaded with the resource description followed by the input-mode rules. The metrics enumeration (KPIs, revenue, players, churn...) is slightly listy but does convey scope and earns its space.

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 return values need not be spelled out, and annotations carry the safety profile. The description covers content and input modes adequately; the remaining gap is the unstated relationship to the write counterpart and the meaning of a 'verified query'.

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 100%, so the baseline is 3, but the description goes further by tying the query and paths inputs to distinct result modes (matching definitions vs. files). The since and organization parameters receive no description-level explanation, so it is not fully complete.

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 ("Returns this organization's own definitions of its metrics, terms and rules, and its verified queries") and enumerates the content types, so the agent knows exactly what it retrieves. It does not explicitly contrast with the write-side sibling write_company_definition, leaving that read/write distinction to be inferred.

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

Usage Guidelines4/5

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

Gives explicit mode-selection rules: "With no input, the index of every definition. With query, matching definitions. With paths, the files." This tells the agent how to pick behavior, but names no alternatives or when-not-to-use conditions relative to the sibling write_company_definition.

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

All Cloche 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.