Semata

Get screening report

get_screening_report

Read-only

Get the content of a screening report: the role criteria, processing counts, and evaluated candidates ranked by score (up to 100 per page). Semata renders the PDF in the browser, so this returns the report as data plus appUrl, the page where the user can download the PDF.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspaceId": "<workspaceId>",
      "batchId": "<batchId>"
    },
    "name": "get_screening_report"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum candidates to include.
`offset`	No	Number of candidates to skip.
`batchId`	Yes	The screening id, from list_batches or get_role.
`workspaceId`	Yes	The workspace id returned by list_workspaces. Use 'personal' for the personal workspace.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish that this is a read-only, non-destructive, closed-world operation. The description adds useful behavioral context beyond annotations: it explains that the result is report data plus an appUrl, and that PDF rendering happens in the browser rather than through this tool. It does not cover auth or rate-limit behavior, but the safety profile is already handled by annotations.

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?

The description is two efficient sentences, front-loads the tool's purpose, and immediately explains the important appUrl/PDF distinction. There is no redundant or filler text.

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?

Because there is no output schema, the description must explain return values, and it does so by listing the report contents and the appUrl. It also covers pagination via 'up to 100 per page.' It is nearly complete, though it could say slightly more about the returned data structure or appUrl usage.

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 parameters are already fully documented in the schema. The description's phrase 'up to 100 per page' aligns with the limit parameter but does not add new semantics beyond what the schema already states for limit, offset, batchId, and workspaceId.

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 uses a specific verb and resource: 'Get the content of a screening report,' and lists the main contents (role criteria, processing counts, ranked candidates). It is clear what the tool does, but it does not explicitly distinguish itself from sibling report tools such as get_batch, get_candidate_report, or get_hiring_report.

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?

Usage is implied by the resource name and by the explanation that the report is returned as data plus an appUrl for PDF download. However, the description does not state when to use this tool versus alternatives or when not to use it.

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

All Semata 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.

Resources

Need Help?