SCModeling

get_sc_theory

Read-onlyIdempotent

Reference guide to supply-chain simulation concepts: ordering policies, BOM, FDD formulas, event-driven simulation. Pure static text — no engine call, deterministic output. Use this when the user asks a conceptual 'how does this work' question rather than asking for a number.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`content`	No	MCP content blocks — single text block with the response body

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds 'Pure static text — no engine call, deterministic output,' reinforcing the safe, predictable behavior with no side effects.

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: first defines the tool, second provides usage guidance. No wasted words, front-loaded with essential information.

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

Completeness5/5

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

Given no parameters, comprehensive annotations, and an output schema (exists), the description sufficiently explains the tool's purpose and behavior.

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

Parameters4/5

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

No parameters exist, so schema coverage is 100%. The description does not need to add parameter info; baseline 4 is appropriate.

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 it is a reference guide to supply-chain simulation concepts, listing specific topics (ordering policies, BOM, FDD formulas, event-driven simulation). It distinguishes from sibling tools like run_simulation by noting it provides static text, not numerical output.

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

Usage Guidelines5/5

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

Explicitly says to use when the user asks a conceptual 'how does this work' question rather than for a numerical result. This provides clear guidance on when to use versus alternatives.

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

All SCModeling tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool has a clearly distinct role: listing, describing, explaining, getting results, or running simulation. No two tools overlap in purpose; for example, describe_* and explain_* serve different needs (precomputed detail vs. conceptual reference).

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with underscores: describe_, explain_, get_, list_, run_. The verb indicates the action, and the noun indicates the resource, making it predictable and easy to understand.

Tool Count5/5

With 11 tools, the set is well-scoped for a demonstration-focused supply chain modeling server. It covers listing, describing, explaining, retrieving results, and running a simulation without unnecessary duplication or missing essential operations.

Completeness4/5

The tool surface is comprehensive for querying and running bundled demos, but it lacks create/update/delete operations for models or demos. This is acceptable since the server provides precomputed results, but it represents a minor gap in lifecycle coverage.

Resources

Need Help?