Skip to main content
Glama
Sign In
mcp-server-scf

mcp-server-scf

by MarkAC007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

scf_evidence_file_read

Read-only

Read evidence files to list uploaded items, retrieve a file with its download URL, or check single-file and organization-wide validation results by method.

Instructions

Read an evidence item's files: list them, one file with its download URL, one file's validation result, or the organization's validation summary. Pick with method.

Input Schema

NameRequiredDescriptionDefault
methodYeslist: List all files uploaded or ingested for an evidence item. Returns filename, content type, upload timestamp, validation status, and a pre-signed download URL (15-min expiry). get: Get metadata and a pre-signed download URL (15-min expiry) for a single evidence file. Use to inspect or retrieve a specific uploaded artifact. validation: Get the validation result for a single evidence file: status (valid/warning/partial/invalid), completeness score, individual rule findings, source, and timestamp. validation_summary: Get aggregate evidence validation metrics for the organization dashboard: total files validated, counts by status (valid/warning/partial/invalid), and overall pass rate.
org_idYesOrganization UUID — obtain from scf_list_organizations
file_idNoEvidence file UUID — obtain from scf_list_evidence_files Used by: get, validation.
evidence_idNoEvidence ID (e.g., 'ERL-IAM-001') — obtain from scf_list_evidence Used by: list, get, validation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.1.0

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already establishes the safe-read profile, and the description is consistent with it, adding that results include download URLs and validation outcomes. It does not mention the 15-minute URL expiry, scope breadth, or any rate/consumption caveats, all of which sit only in the schema.

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?

A single front-loaded sentence that enumerates the four modes and closes with the selection instruction — no filler and nothing buried.

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 dispatcher with a fully documented schema and no output schema, the description is nearly complete for selection purposes. The only gap is that the mapping between modes and the optional file_id/evidence_id arguments is left entirely to the schema.

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 coverage is 100%, so the baseline of 3 applies. The description names the method as the discriminator but adds no format, dependency, or required-parameter-pairing detail beyond what the schema already states.

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?

Names a specific verb (read) and resource (an evidence item's files) and enumerates the four concrete result shapes the caller can obtain. It is clearly distinguishable from scf_evidence_file_write by naming the read modes, though it does not explicitly contrast itself with scf_evidence_read.

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?

"Pick with method" signals that the enum is the selector, but the description itself gives no when-to-use criteria across the four modes or against the sibling evidence tools. The real guidance lives in the method enum's schema descriptions rather than in the description text.

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