yarrowdalegraph

Overview Schema Source Related Servers Discussions Admin

score_graph

Score fraud risk for every entity in a graph by propagating analyst seeds and model priors across relationships. Falls back to structural scoring when the model is unavailable.

Instructions

Score fraud risk for every entity in a graph by propagating analyst seeds and model priors across relationships. Degrades to a deterministic structural fallback when the model is unavailable.

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": {
      "graph": "<graph>"
    },
    "name": "score_graph"
  }
}

Input Schema

Name	Required	Description	Default
`graph`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The description explains the core computation and the fallback behavior when the model is unavailable, but it does not disclose side effects, read-only semantics, error behavior, or expected outputs. With no annotations, more behavioral detail would be beneficial.

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 concise, using two straightforward sentences. It front-loads the primary purpose and follows with the fallback behavior, with no redundant or extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The complex nested graph schema with node kinds, seeds, edge weights, and attributes is not elaborated. There is also no output schema or description of return values, making the description incomplete for fully understanding how to construct inputs or interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain individual parameters such as 'seed', 'attributes', 'weight', or 'relation'. It provides general context about graph relationships but leaves parameter meaning largely to inference.

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 verb 'Score fraud risk', the resource 'every entity in a graph', and the method 'propagating analyst seeds and model priors across relationships'. It also mentions the deterministic fallback, making the tool's intent unmistakable.

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?

It provides clear context for when to use the tool: whenever fraud risk scores are needed for entities in a graph. There are no explicit exclusions, but no sibling tools exist, so the absence of explicit alternative guidance is acceptable.

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

score_graphA