Skip to main content
Glama
ChronulusAI

Chronulus MCP Server

Official

get_risk_assessment_scorecard

Retrieve risk assessment scorecards to evaluate forecasting safety concerns and justify warnings about prediction implications. Use session IDs to access markdown or JSON formatted reports.

Instructions

A tool that retrieves the risk assessment scorecard for the Chronulus Session in Markdown format

When to use this tool:

  • Use this tool when the use asks about the risk level or safety concerns of a forecasting use case

  • You may also use this tool to provide justification to a user if you would like to warn them of the implications of what they are asking you to forecasting or predict.

How to use this tool:

  • Make sure you have a session_id for the forecasting or prediction use case

  • When displaying the scorecard markdown for the user, you should use an MDX-style React component

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesThe session_id for the forecasting or prediction use case
as_jsonYesIf true, returns the scorecard in JSON format, otherwise returns a markdown formatted scorecard

Implementation Reference

  • The handler function that implements the core logic of the 'get_risk_assessment_scorecard' tool. It loads a Chronulus session using the provided session_id, generates the risk scorecard either as markdown or JSON based on the 'as_json' flag, and returns the content.
    async def get_risk_assessment_scorecard(
            session_id: Annotated[str, Field(description="The session_id for the forecasting or prediction use case")],
            as_json:  Annotated[bool, Field(description="If true, returns the scorecard in JSON format, otherwise returns a markdown formatted scorecard")]
    ) -> str:
        """Get the risk assessment scorecard for the Session
    
        Args:
            session_id (str): The session_id for the forecasting or prediction use case.
            as_json (bool): If true, returns the scorecard in JSON format, otherwise returns a markdown formatted scorecard
    
        Returns:
            str: a risk assessment scorecard in the specified format.
        """
    
        chronulus_session = Session.load_from_saved_session(session_id=session_id, verbose=False)
        scorecard_md = chronulus_session.risk_scorecard(width='100%')
        if as_json:
            content = json.dumps(chronulus_session.scorecard.model_dump())
        else:
            content = scorecard_md
        return content
  • Registers the 'get_risk_assessment_scorecard' tool with the FastMCP server instance, associating it with a detailed usage description.
    mcp.add_tool(get_risk_assessment_scorecard, description=GET_RISK_ASSESSMENT_SCORECARD_DESCRIPTION)
  • Defines the detailed description string used for the tool's schema/documentation, outlining when and how to use the tool, including input requirements like session_id.
    GET_RISK_ASSESSMENT_SCORECARD_DESCRIPTION = """
    A tool that retrieves the risk assessment scorecard for the Chronulus Session in Markdown format
    
    When to use this tool:
    - Use this tool when the use asks about the risk level or safety concerns of a forecasting use case
    - You may also use this tool to provide justification to a user if you would like to warn them of the implications of 
        what they are asking you to forecasting or predict.
    
    How to use this tool:
    - Make sure you have a session_id for the forecasting or prediction use case
    - When displaying the scorecard markdown for the user, you should use an MDX-style React component
    """
  • Imports the 'get_risk_assessment_scorecard' function from the session module, making it available for registration.
    from .session import create_chronulus_session, get_risk_assessment_scorecard
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool retrieves data (implying read-only) and mentions output formats (Markdown/JSON), but lacks details on permissions, rate limits, error handling, or what the scorecard contains. It adds some context (e.g., format options) but doesn't fully compensate for the missing annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections ('When to use this tool' and 'How to use this tool'), and sentences are purposeful. However, it includes implementation advice ('use an MDX-style React component') that may be unnecessary for tool selection, slightly reducing efficiency.

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

Completeness3/5

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

Given no annotations and no output schema, the description is moderately complete. It covers purpose, usage, and basic parameters, but lacks details on behavioral traits (e.g., auth, errors) and output structure. For a tool with 2 parameters and no structured output info, it should provide more context on what the scorecard contains or how to interpret it.

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 schema already documents both parameters ('session_id' and 'as_json'). The description adds minimal value beyond the schema: it mentions 'Markdown format' and implies JSON as an alternative, but doesn't explain parameter interactions or provide additional semantics. Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the tool's purpose: 'retrieves the risk assessment scorecard for the Chronulus Session in Markdown format'. It specifies the verb ('retrieves'), resource ('risk assessment scorecard'), and format ('Markdown format'), though it doesn't explicitly distinguish it from sibling tools like 'save_forecast' or 'save_prediction_analysis_html', which are write operations.

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?

The description provides explicit guidance on when to use this tool: 'when the user asks about the risk level or safety concerns of a forecasting use case' and 'to provide justification... if you would like to warn them'. It clearly defines the context for usage, though it doesn't mention alternatives or exclusions, which is acceptable given the specificity of the use cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ChronulusAI/chronulus-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server