Skip to main content
Glama

Last Price

list_functions

Read-onlyIdempotent

List the pricing functions registered for the authenticated tenant.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPage size. Defaults to 50; the API caps it at 100.
offsetNoRows to skip. Defaults to 0.
statusNoOnly functions in this status.
is_builtinNoTrue for built-in functions only, false for the tenant's own only.
execution_typeNoOnly functions of this execution type.

Output Schema

NameRequiredDescriptionDefault
itemsNo
messageNoA short sentence about the result that an agent can show its person.
functionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / message / description
      Added value: +"A short sentence about the result that an agent can show its person."
  2. Changed5 schema fields changed
    • addedInput schema / properties / execution_type
      Added value: +{
      +  "description": "Only functions of this execution type.",
      +  "enum": [
      +    "rule_based",
      +    "ml_model",
      +    "llm_prompt",
      +    "external_api",
      +    "composite"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / is_builtin
      Added value: +{
      +  "description": "True for built-in functions only, false for the tenant's own only.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Page size. Defaults to 50; the API caps it at 100.",
      +  "maximum": 100,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Rows to skip. Defaults to 0.",
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / status
      Added value: +{
      +  "description": "Only functions in this status.",
      +  "enum": [
      +    "draft",
      +    "review",
      +    "active",
      +    "inactive",
      +    "deprecated"
      +  ],
      +  "type": "string"
      +}
  3. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "functions": {
      +      "type": "array"
      +    },
      +    "items": {
      +      "type": "array"
      +    },
      +    "message": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  4. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description's only addition is the tenant scoping, which largely restates openWorldHint=false; it says nothing about pagination behavior, default ordering, or result caps beyond what the schema implies.

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?

A single front-loaded sentence with zero filler. It is efficient, though its brevity comes at the cost of any operational detail.

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?

With five optional filter/pagination params, rich annotations, and an output schema, the description does the minimum: it identifies the resource and tenant scope. It never explains that all five params are optional combinable filters or how paging should be driven, leaving that entirely to the schema.

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% with well-documented limit/offset/status/is_builtin/execution_type fields, so the baseline of 3 applies. The description adds no filtering or pagination semantics beyond what the schema already states.

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?

Clear verb+resource ("List the pricing functions") with a useful scope qualifier ("registered for the authenticated tenant"). No sibling tool overlaps with function listing, so explicit differentiation is unnecessary, though the description never says what a 'pricing function' is relative to the compute_price/verify_price siblings.

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

Usage Guidelines2/5

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

No when-to-use guidance, no mention of when to prefer get-by-id or compute_price instead, and no hint that results are paginated or filtered via the optional params. The usage context is only inferable from the name.

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