Skip to main content
Glama

principia.constructs.measures

Read-only

Return instruments that measure a given construct, ranked by composite score (reliability + validity + literature usage + recency). Optional filters: min_reliability, cross_cultural_only, length_lte. Read-only — no mutation (curator-policy D4).

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": {
      "construct_id": "<construct_id>"
    },
    "name": "principia.constructs.measures"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
length_lteNo
construct_idYes
min_reliabilityNo
cross_cultural_onlyNo

Output Schema

NameRequiredDescriptionDefault
itemsYes
totalYes
construct_idYes
generated_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / items / items / properties / deploy_url / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / items / items / properties / deploy_url / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / items / items / properties / recency_year / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / items / items / properties / recency_year / type
      Added value: +[
      +  "number",
      +  "null"
      +]
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The description discloses how results are ranked (reliability + validity + literature usage + recency), which is genuine behavioral context not present in annotations. However, 'Read-only — no mutation (curator-policy D4)' largely restates readOnlyHint/destructiveHint=false; the added value is the policy citation rather than new operational information. Nothing is said about how ties are broken or how many results are returned by default.

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?

Two dense sentences with the core behavior front-loaded and filters enumerated compactly; nothing is padded. The trailing policy clause is the only piece that could be trimmed as redundant with annotations.

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?

An output schema exists, so return-value explanation is not required, and the ranking formula plus filters cover the main call shape. The significant gap is the required construct_id: nothing tells the agent what identifier format is expected or that principia.constructs.resolve/lookup should be used to obtain one, which matters for a tool that cannot be invoked without 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 0%, so the description carries the burden, and it does explain three optional filters (min_reliability, cross_cultural_only, length_lte) with enough naming to be self-evident. It says nothing about limit or about what form construct_id takes, so two of five parameters remain undocumented in both schema and description.

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?

States a specific verb and resource ('Return instruments that measure a given construct') plus the ranking basis, so the agent knows this is a construct-scoped retrieval rather than a general instrument search. It stops short of naming a sibling such as principia.instruments.search to contrast against, leaving the boundary to be inferred from the construct scoping.

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 implied by the required construct_id ('given construct') and the filter list hints at narrowing scenarios, but there is no explicit when-to-use guidance, no exclusion relative to principia.instruments.search or principia.measures.list, and no note on when the ranked composite ordering should be preferred over a plain lookup.

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