Skip to main content
Glama
MarkAC007

mcp-server-scf

by MarkAC007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

scf_list_evidence

Read-only

List evidence items tracked against controls, returning tracking status, maturity level, and linked controls. Filter by system, team, function, or owner.

Instructions

List evidence items tracked against an organization's controls. Returns each item's tracking status, maturity level, and linked controls. Optionally filter by system.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
org_idYesOrganization UUID — obtain from scf_list_organizations
team_idNoFilter to evidence this team is assigned to, accountable or consulted — obtain from scf_list_teams
my_teamsNoFilter to evidence assigned to any team the caller belongs to; intersects with team_id rather than overriding it. 'The caller' is the API key's identity; on a self-hosted instance that is a service account on no team, so this returns nothing — use team_id instead.
system_idNoSystem UUID to filter by — obtain from scf_list_systems
function_idNoFilter to evidence assigned to any team aligned to this function — obtain from scf_list_functions
accountable_owner_typeNoFilter by the accountable team's primary owner: 'internal' or 'external_contractor'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv3.6.0
    • addedInput schema / properties / accountable_owner_type
      Added value: +{
+  "description": "Filter by the accountable team's primary owner: 'internal' or 'external_contractor'",
+  "enum": [
+    "internal",
+    "external_contractor"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / function_id
      Added value: +{
+  "description": "Filter to evidence assigned to any team aligned to this function — obtain from scf_list_functions",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}
    • addedInput schema / properties / my_teams
      Added value: +{
+  "default": false,
+  "description": "Filter to evidence assigned to any team the caller belongs to; intersects with team_id rather than overriding it. 'The caller' is the API key's identity; on a self-hosted instance that is a service account on no team, so this returns nothing — use team_id instead.",
+  "type": "boolean"
+}
    • addedInput schema / properties / team_id
      Added value: +{
+  "description": "Filter to evidence this team is assigned to, accountable or consulted — obtain from scf_list_teams",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}
  2. First observedv1.7.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, so the safety profile is covered. The description adds useful behavioral detail beyond that: results include tracking status, maturity, and linked controls, and system filtering is optional. It does not mention pagination or response ordering, but for a read-only list this is a minor gap.

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 sentences, front-loaded with the action and scope, followed by return fields and the single optional filter. No filler or repetition of schema details.

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 list with one required and five optional, all richly documented parameters, the description plus annotations are largely sufficient. It tells the agent what fields come back and that system is a filter, though it omits pagination/limits and does not route between sibling evidence-list tools.

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%, and each parameter has a rich description, including provenance hints like 'obtain from scf_list_organizations' and the my_teams caveat. The description's 'optionally filter by system' merely restates system_id, adding no new meaning, so baseline 3 applies.

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?

The description names a specific verb and resource — 'List evidence items tracked against an organization's controls' — and enumerates returned fields (tracking status, maturity level, linked controls), which separates this from file/task/catalog evidence siblings. It does not explicitly name a comparator sibling, so while clearly scoped, it stops shy of the strongest differentiation.

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

Usage Guidelines2/5

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

No guidance about when to choose this over scf_list_evidence_files, scf_list_evidence_catalog, or scf_get_evidence; it only notes an optional system filter. The intended use is implied as an org-level evidence overview, but exclusions or alternatives are absent.

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

Deploy Server

Other Tools