Cortex

Listscorecards

listScorecards

List all scorecards in the organization with optional filtering. View scorecard configurations to understand quality standards, compliance requirements, and maturity models. Supports filtering by groups, entities, and teams to find relevant scorecards.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	Yes	Page number to return, 0-indexed. Default 0.
`teams`	No	Filter based on team (either tags or CIDs). Accepts a comma-delimited list of team tag or CIDs, please use only one type of identifier
`groups`	No	Filter based on groups, which correspond to the `x-cortex-groups` field in the Catalog Descriptor. Accepts a comma-delimited list of groups
`context`	Yes	Explain why you're invoking this tool now and how its output will be used. Then state how this call supports your overall objective and fits into your broader plan across all tool calls (e.g., why this tool vs. others, and what step it unblocks). Never share any personal details or sensitive information.
`entities`	No	Filter based on entity (either tags or CIDs). Accepts a comma-delimited list of entity tag or CIDs, please use only one type of identifier
`pageSize`	Yes	Number of results to return per page, between 1 and 1000. Default 250.
`session_id`	Yes	Session continuity handle, one of two values: the ses_ ID issued for the task underway, or start. This server cannot link your calls between requests on its own, so session continuity travels in this parameter instead. If you were handed a session_id for this task — for example by the agent that spawned you — send that exact value from your first call. Otherwise send start on your first call; the server will issue an opaque correlation ID in the mcp_session field of the result, or in a text block at the start of the result beginning [session_id issued. Then send that exact ses_ value on every later call and hand it to any subagents working the same task. start always begins a new, unrelated task — never send it mid-task. If you send a value this server does not recognize, the result reports it: mcp_session.status of unrecognized, or a text block beginning [session_id unrecognized; re-send the ID issued for this task, or start if none was issued yet. Never invent a ses_ value.
`showDrafts`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 25, 2026

addedInput schema / properties / session_id

Added value: +{
+  "description": "Session continuity handle, one of two values: the ses_ ID issued for the task underway, or start. This server cannot link your calls between requests on its own, so session continuity travels in this parameter instead. If you were handed a session_id for this task — for example by the agent that spawned you — send that exact value from your first call. Otherwise send start on your first call; the server will issue an opaque correlation ID in the mcp_session field of the result, or in a text block at the start of the result beginning [session_id issued. Then send that exact ses_ value on every later call and hand it to any subagents working the same task. start always begins a new, unrelated task — never send it mid-task. If you send a value this server does not recognize, the result reports it: mcp_session.status of unrecognized, or a text block beginning [session_id unrecognized; re-send the ID issued for this task, or start if none was issued yet. Never invent a ses_ value.",
+  "pattern": "^(start|ses_[0-9A-Za-z]{27})$",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "page",
-  "pageSize",
-  "context"
-]New value: +[
+  "page",
+  "pageSize",
+  "session_id",
+  "context"
+]

First observedJan 31, 2026

TDQS

A3.6/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 of behavioral disclosure. It mentions optional filtering and lists filter dimensions (groups, entities, teams), and states the tool returns 'scorecard configurations.' However, it does not mention pagination behavior, that results are paginated via page/pageSize, or how showDrafts affects results. For a list operation without annotations, this is a moderate disclosure but leaves gaps.

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?

The description is three sentences and front-loads the core purpose ('List all scorecards in the organization'). It is efficient, though the second sentence about 'viewing configurations' is slightly redundant with the purpose but adds context on why it might be used. No filler or repetition of the tool name.

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?

With 8 parameters and no output schema or annotations, the description covers the main functionality (listing and filtering) but omits details like pagination, session_id handling (though the schema covers it), and the effect of showDrafts. The tool is moderately complex, and while the schema fills in most gaps, the description does not fully explain the complete behavior expected when calling the tool.

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 88%, so the input schema already documents most parameters. The description mentions filtering by groups, entities, and teams, which aligns with the schema but adds little beyond it. It does not explain page/pageSize, session_id, context, or showDrafts beyond what the schema already states. Baseline of 3 is appropriate given the high schema coverage.

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?

The description clearly states the tool lists all scorecards in the organization, with optional filtering. It names the resource ('scorecards') and the verb ('list'), and distinguishes itself from siblings like getScorecard (which retrieves a single scorecard) and listScorecardScores (which lists scores). The mention of 'view scorecard configurations' reinforces the specific use case.

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?

The description implies usage by saying 'List all scorecards in the organization' and mentions filtering, but does not explicitly state when to use this tool versus alternatives like listScorecardScores or getScorecard. It lacks explicit 'when not to use' guidance or comparisons to sibling tools. The purpose is implied, but no exclusions are provided.

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

All Cortex tools Inspect

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

Need Help?