Close Knit

List school measures

list_school_measures

Read-onlyIdempotent

Moved: use describe_data(kind: "school"). Answers until 2026-11-30.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_school_measures"
  }
}

Input Schema

Name	Required	Description	Default
`intent`	No	[input value] Optional, one to three sentences you write: what the user is looking for with this call and the criteria that matter, e.g. '2-bed rental near King's Cross, up to £2,500 a month, quiet, good primary schools'. Close Knit reads these to improve its answers. Your own summary, not the user's words or the chat; never names, contact details, exact addresses or family circumstances.
`rate_previous`	No	[input value] Optional: your rating of an earlier Close Knit answer, by the callId it carried (none: the last answer). Send it with your next Close Knit call every time you have used an answer: rating 1-5 for how well it served the user's request, what was good, what was bad or missing, and the fix you would want.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedNov 5, 2026

changedInput schema / $defs / RatePrevious / properties / bad / description

Previous value: -"What was wrong, missing or confusing."New value: +"[input value] What was wrong, missing or confusing."

changedInput schema / $defs / RatePrevious / properties / call_id / description

Previous value: -"The callId of the answer you are rating; leave it out when answers carry none."New value: +"[id] The callId of the answer you are rating; leave it out when answers carry none."

changedInput schema / $defs / RatePrevious / properties / fix / description

Previous value: -"The change to the tool or its answer you would want."New value: +"[input value] The change to the tool or its answer you would want."

changedInput schema / $defs / RatePrevious / properties / good / description

Previous value: -"What was useful in the answer."New value: +"[input value] What was useful in the answer."

changedInput schema / $defs / RatePrevious / properties / rating / description

Previous value: -"1 = useless or wrong, 3 = usable with gaps, 5 = exactly what was needed."New value: +"[input value] 1 = useless or wrong, 3 = usable with gaps, 5 = exactly what was needed."

changedInput schema / properties / intent / description

Previous value: -"Optional, one to three sentences you write: what the user is looking for with this call and the criteria that matter, e.g. '2-bed rental near King's Cross, up to £2,500 a month, quiet, good primary schools'. Close Knit reads these to improve its answers. Your own summary, not the user's words or the chat; never names, contact details, exact addresses or family circumstances."New value: +"[input value] Optional, one to three sentences you write: what the user is looking for with this call and the criteria that matter, e.g. '2-bed rental near King's Cross, up to £2,500 a month, quiet, good primary schools'. Close Knit reads these to improve its answers. Your own summary, not the user's words or the chat; never names, contact details, exact addresses or family circumstances."

changedInput schema / properties / rate_previous / description

Previous value: -"Optional: your rating of an earlier Close Knit answer, by the callId it carried (none: the last answer). Send it with your next Close Knit call every time you have used an answer: rating 1-5 for how well it served the user's request, what was good, what was bad or missing, and the fix you would want."New value: +"[input value] Optional: your rating of an earlier Close Knit answer, by the callId it carried (none: the last answer). Send it with your next Close Knit call every time you have used an answer: rating 1-5 for how well it served the user's request, what was good, what was bad or missing, and the fix you would want."

Changed6 schema fields changedOct 30, 2026

addedInput schema / $defs / RatePrevious / properties / call_id / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / $defs / RatePrevious / properties / call_id / default
```
Added value: +null
```

changedInput schema / $defs / RatePrevious / properties / call_id / description

Previous value: -"The callId of the answer you are rating."New value: +"The callId of the answer you are rating; leave it out when answers carry none."

removedInput schema / $defs / RatePrevious / properties / call_id / type
```
Removed value: -"string"
```

changedInput schema / $defs / RatePrevious / required

Previous value: -[
-  "call_id",
-  "rating"
-]New value: +[
+  "rating"
+]

changedInput schema / properties / rate_previous / description

Previous value: -"Optional: your rating of an earlier Close Knit answer, by the callId it carried. Send it with your next Close Knit call every time you have used an answer: rating 1-5 for how well it served the user's request, what was good, what was bad or missing, and the fix you would want."New value: +"Optional: your rating of an earlier Close Knit answer, by the callId it carried (none: the last answer). Send it with your next Close Knit call every time you have used an answer: rating 1-5 for how well it served the user's request, what was good, what was bad or missing, and the fix you would want."

AddedOct 29, 2026

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-open-world), so the bar is lower. The description adds a genuinely useful behavioral fact the annotations do not carry: a hard availability cutoff of 2026-11-30. It says nothing about result format or pagination, but an output schema exists to cover that.

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

Conciseness5/5

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

Two short sentences, front-loaded with the migration directive before the expiry detail. No filler and nothing that could be cut without losing information.

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?

For a deprecation stub with full schema coverage and an output schema, the essentials are present: where to go and how long this remains callable. The only gap is whether callers should still use it at all before the cutoff, which the agent must assume.

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 100% across both optional parameters (intent, rate_previous), and the description adds no parameter guidance whatsoever. Baseline 3 applies since the schema does all the explanatory work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never states what the tool does; it only announces that it has moved and that the replacement is describe_data(kind: "school"). The agent must infer from the name and the migration target that this returns school measures, which is adequate but indirect. It does effectively distinguish itself from siblings by pointing at exactly one successor.

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?

It gives an explicit alternative and the argument to pass ('use describe_data(kind: "school")'), which is exactly the routing decision an agent needs. The sunset date ('Answers until 2026-11-30') implies the tool still works in the interim, but it does not say whether new calls should be routed away now or only after that date.

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

All Close Knit tools Inspect

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.