Skip to main content
Glama

Compile sustainability disclosure

compile_disclosure

Compile a deterministic, cited disclosure draft from supplied company facts and an optional verified GHG-ledger result. Missing required datapoints remain explicit gaps; no prose or values are fabricated. Frameworks: esrs-e1, ifrs-s2, sec-climate, tnfd, ca-sb253 (California SB 253 first-cycle Scope 1 and 2); list_frameworks gives the current set. If a call fails, the response includes first_call_help. Example arguments: {"framework": "esrs-e1", "company_facts": {"company_name": "Acme Climate Works", "reporting_period": "2026", "transition_plan": {"status": "board-approved", "target_year": 2035}, "climate_targets": {"scope": "Scopes 1-3", "target": "50% by 2035"}, "ghg_intensity": {"value": "0.012", "unit": "tCO2e/USDm revenue"}}, "options": {"applicability": {"framework": "esrs-e1", "applies": true, "reason": "company is in CSRD scope"}}}

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "compile_disclosure"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNoMust hold `applicability`: {framework: the same framework id, applies: true, reason: why it applies to this company}.
frameworkNoWhich disclosure to draft. One of: ca-sb253, esrs-e1, ifrs-s2, sec-climate, tnfd.
ghg_resultNoOptional. The `data` object of a ghg-ledger calculate_inventory result, passed unchanged; it fills the emission datapoints and is verified before use.
request_idNoOptional. Your id for this call. Repeat it to retry safely: the same request_id is never charged twice.
payment_refNoOptional. A paid credit or payment reference, used only after the free daily calls. Leave it out to use the free tier or a seat.
company_factsNoFacts about the company, as an object. Only supplied facts are used; anything missing is listed as a gap. Keys read, by framework: ca-sb253: assurance_status, company_name, ghg_methodology, organizational_boundary, reporting_period; esrs-e1: climate_targets, company_name, ghg_intensity, reporting_period, transition_plan; ifrs-s2: climate_governance, climate_resilience, climate_strategy, climate_targets, company_name, reporting_period, risk_management_process; sec-climate: board_oversight, climate_targets, company_name, management_role, material_climate_risks, reporting_period, risk_management_process; tnfd: company_name, leap_process, nature_dependencies_and_impacts, nature_governance, nature_metrics, nature_risks_and_opportunities, nature_targets, priority_locations, reporting_period.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / payment_ref / description
      Added value: +"Optional. A paid credit or payment reference, used only after the free daily calls. Leave it out to use the free tier or a seat."
    • addedInput schema / properties / request_id / description
      Added value: +"Optional. Your id for this call. Repeat it to retry safely: the same request_id is never charged twice."
  2. Changed4 schema fields changed
    • addedInput schema / properties / company_facts / description
      Added value: +"Facts about the company, as an object. Only supplied facts are used; anything missing is listed as a gap. Keys read, by framework: ca-sb253: assurance_status, company_name, ghg_methodology, organizational_boundary, reporting_period; esrs-e1: climate_targets, company_name, ghg_intensity, reporting_period, transition_plan; ifrs-s2: climate_governance, climate_resilience, climate_strategy, climate_targets, company_name, reporting_period, risk_management_process; sec-climate: board_oversight, climate_targets, company_name, management_role, material_climate_risks, reporting_period, risk_management_process; tnfd: company_name, leap_process, nature_dependencies_and_impacts, nature_governance, nature_metrics, nature_risks_and_opportunities, nature_targets, priority_locations, reporting_period."
    • addedInput schema / properties / framework / description
      Added value: +"Which disclosure to draft. One of: ca-sb253, esrs-e1, ifrs-s2, sec-climate, tnfd."
    • addedInput schema / properties / ghg_result / description
      Added value: +"Optional. The `data` object of a ghg-ledger calculate_inventory result, passed unchanged; it fills the emission datapoints and is verified before use."
    • addedInput schema / properties / options / description
      Added value: +"Must hold `applicability`: {framework: the same framework id, applies: true, reason: why it applies to this company}."
  3. Changed8 schema fields changed
    • removedInput schema / properties / company_facts / additionalProperties
      Removed value: -true
    • addedInput schema / properties / company_facts / anyOf
      Added value: +[
      +  {
      +    "additionalProperties": true,
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / company_facts / default
      Added value: +null
    • removedInput schema / properties / company_facts / type
      Removed value: -"object"
    • addedInput schema / properties / framework / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / framework / default
      Added value: +null
    • removedInput schema / properties / framework / type
      Removed value: -"string"
    • removedInput schema / required
      Removed value: -[
      -  "framework",
      -  "company_facts"
      -]
  4. Changed1 schema field changed
    • addedInput schema / properties / request_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Request Id"
      +}
  5. Changed1 schema field changed
    • addedInput schema / properties / payment_ref
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Payment Ref"
      +}
  6. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-destructive, non-idempotent call, and the description adds meaningful behavior beyond that: determinism, no fabrication of prose or values, explicit gap reporting, and verification of the GHG result before use. It also discloses the failure behavior (first_call_help in the response). It does not itself address retry/charging semantics, which live 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.

Conciseness4/5

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

The behavioral guarantees and framework list are front-loaded, and the example is placed last where it belongs. The example is long but earns its space by demonstrating nested structures; the only redundancy is restating the framework ids already given in the schema.

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?

With an output schema present, the description needn't explain return values, and it covers the remaining agent-facing unknowns: which frameworks exist, how gaps are handled, what ghg_result should be, and where to look when a call fails. Nothing needed to invoke this six-parameter tool correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the worked example adds real meaning the schema cannot: it shows the nested shape of transition_plan, climate_targets, ghg_intensity (with value/unit), and the required applicability object inside options. That materially helps an agent construct a valid call.

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 first sentence states a specific verb and artifact ('Compile a deterministic, cited disclosure draft') plus its inputs (company facts, optional verified GHG-ledger result). It enumerates the exact framework ids and points to list_frameworks for the current set, so an agent can distinguish it from get_framework/describe_agent without opening a schema.

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 gives clear context for use: supply company facts plus an optional ghg_result, and missing datapoints stay as explicit gaps. It also routes to list_frameworks for the framework set and notes that failures return first_call_help. It stops short of stating when to prefer this over verify_result or get_framework.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.