Claimora

get_innovation_flags

List innovation flags, strongest first.

Use this when you want links between claims rather than the claims themselves.
Returns flag id, domain, summary, strength, and the claim ids on each path.
Example: get_innovation_flags(domain="ai-ml", min_strength=0.5, limit=10).
Example: get_innovation_flags(domain="quantum", min_strength=0.8, limit=5).

Input Schema

Name	Required	Description
`limit`	No	Page size. Example: 10.
`domain`	No	Restrict flags to one domain. Example: ai-ml.
`offset`	No	Number of hits to skip. Example: 0.
`min_strength`	No	Drop flags below this strength, from 0 to 1. Example: 0.5.

Output Schema

Name	Required	Description	Default
`page`	Yes
`flags`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 26, 2026
- changedInput schema / properties / domain / description
```
Previous value: -"Restrict flags to one domain."New value: +"Restrict flags to one domain. Example: ai-ml."
```
- addedInput schema / properties / domain / examples
```
Added value: +[
+  "ai-ml"
+]
```
- addedInput schema / properties / limit / description
```
Added value: +"Page size. Example: 10."
```
- addedInput schema / properties / limit / examples
```
Added value: +[
+  10
+]
```
- changedInput schema / properties / min_strength / description
```
Previous value: -"Drop flags below this strength."New value: +"Drop flags below this strength, from 0 to 1. Example: 0.5."
```
- addedInput schema / properties / min_strength / examples
```
Added value: +[
+  0.5
+]
```
- addedInput schema / properties / offset / description
```
Added value: +"Number of hits to skip. Example: 0."
```
- addedInput schema / properties / offset / examples
```
Added value: +[
+  0
+]
```
First observedOct 25, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It does disclose useful behavior: results are ordered strongest-first and entries below min_strength are dropped. It says nothing about pagination semantics beyond the schema, permissions, or result size, which keeps it at adequate rather than rich.

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 opening line and usage sentence are well front-loaded, but the second example ('quantum', 0.8, 5) repeats the structure of the first and adds almost nothing, and the return-field list partly duplicates the existing output schema.

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 read-only, zero-required-parameter listing tool with a full output schema and 100% schema coverage, the definition covers purpose, ordering, filtering behavior, and return shape. The main remaining gap is a fuller explanation of what a 'flag' represents conceptually.

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%, so the baseline is 3. The examples reinforce how domain, min_strength, and limit are combined (e.g. domain="ai-ml", min_strength=0.5, limit=10), but they add no semantic detail the schema lacks, such as whether domain accepts wildcards or what strength measures.

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

Purpose5/5

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

States a specific verb and resource ('List innovation flags') plus ordering ('strongest first'), and the second sentence distinguishes the output from the claim-oriented siblings ('links between claims rather than the claims themselves'), so an agent can tell it apart from query_claims and get_evidence without reading a schema.

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?

'Use this when you want links between claims rather than the claims themselves' gives a clear selection condition against the claim/evidence tools, and two worked examples show realistic call shapes. It stops short of an explicit when-not statement, so it is not a full 5.

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

All Claimora tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?