Skip to main content
Glama

get_esg_benchmark

Read-only

ESG benchmarks by sector — carbon intensity Scope 1/2, net zero commitments, SBTi alignment, board independence, pay equity, and ESG composite scores. Sources: EPA GHGRP, MSCI ESG methodology. For sustainability agents and ESG analysts. $0.02 USDC per call.

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": "get_esg_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
focusNo
sectorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds two behavioral facts not present in structured fields: the upstream provenance (EPA GHGRP, MSCI ESG methodology) which tells the agent how authoritative the numbers are, and a per-call price of $0.02 USDC, which is an operational constraint the agent must budget for. It does not describe return granularity or latency, keeping it short of a 5.

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?

Content is front-loaded: metric coverage first, then provenance, then audience, then price. Every clause carries distinct information and there is no filler. The em-dash metric list is dense but readable; a slightly clearer separation of the pricing/audience notes would improve it marginally.

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?

For a read-only benchmark lookup with two optional enum parameters and no output schema, the definition covers what data exists, where it comes from, and what it costs. The remaining gap is that it never states what happens when sector is omitted or at what granularity results are returned (sector-level vs company-level), which matters given there is no output schema to fall back on.

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 0%, so the description carries the burden, and it only partially does: 'by sector' hints at the sector parameter and the metric list implies the carbon/social/governance split for focus. However, neither parameter is named, the meaning of the 'all' enum value as a default is not explained, and nothing says how focus and sector interact. The enums make values self-evident, so this is adequate but with a clear gap.

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 names a specific resource and scope: 'ESG benchmarks by sector', then enumerates the concrete metrics returned (Scope 1/2 carbon intensity, net zero commitments, SBTi alignment, board independence, pay equity, composite scores). That is far more informative than a restated title. It does not explicitly contrast itself with siblings, but the ESG/sustainability domain is unambiguous against the other benchmark tools.

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 only implied through the audience line ('For sustainability agents and ESG analysts'), which signals the appropriate caller but not the decision boundary. There is no statement of when to prefer this over a sibling such as get_climate_risk_benchmark, and no prerequisites or exclusions. An agent can infer fit, but must do the reasoning itself.

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.

Resources