Skip to main content
Glama

Service Read Tool

service-read
Read-only

List or show services, or get_task_templates for a service's current reusable checklist and template IDs. Lists support filtering, sorting and pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for "list". Default 1.
sortNoSort fields for "list". Append :asc or :desc for direction (default :asc). Example: ["created_at:desc"]. Available fields: id, intake_form_id, is_taxable, name, description, image, recurring, price, max_active_requests, pretty_price, currency, f_price, f_period_l, f_period_t, r_price, r_period_l, r_period_t, recurring_action, multi_order, request_orders, option_categories, option_variants, deadline, public, sort_order, braintree_plan_id, group_quantities, folder_id, metadata, hoth_product_key, hoth_package_name, created_at, updated_at, provider_id, provider_service_id, deleted_at, services.id, services.intake_form_id, services.is_taxable, services.name, services.description, services.image, services.recurring, services.price, services.max_active_requests, services.pretty_price, services.currency, services.f_price, services.f_period_l, services.f_period_t, services.r_price, services.r_period_l, services.r_period_t, services.recurring_action, services.multi_order, services.request_orders, services.option_categories, services.option_variants, services.deadline, services.public, services.sort_order, services.braintree_plan_id, services.group_quantities, services.folder_id, services.metadata, services.hoth_product_key, services.hoth_package_name, services.created_at, services.updated_at, services.provider_id, services.provider_service_id, services.deleted_at, orders, invoice_items, addons, parent_services, folder, reseller_provider, tasks, workflowSteps, intakeForm, onboardingForms, addon_orders, getFieldsAttribute, employees, audits, morphMetadata, media, logs.
limitNoResults per page for "list". Default 20, max 100.
actionYesAction to perform.
filtersNoPurity filter object for "list". Keys are field names, values are operator objects. Example: {"status":{"$eq":1}}. Available fields: id, intake_form_id, is_taxable, name, description, image, recurring, price, max_active_requests, pretty_price, currency, f_price, f_period_l, f_period_t, r_price, r_period_l, r_period_t, recurring_action, multi_order, request_orders, option_categories, option_variants, deadline, public, sort_order, braintree_plan_id, group_quantities, folder_id, metadata, hoth_product_key, hoth_package_name, created_at, updated_at, provider_id, provider_service_id, deleted_at, services.id, services.intake_form_id, services.is_taxable, services.name, services.description, services.image, services.recurring, services.price, services.max_active_requests, services.pretty_price, services.currency, services.f_price, services.f_period_l, services.f_period_t, services.r_price, services.r_period_l, services.r_period_t, services.recurring_action, services.multi_order, services.request_orders, services.option_categories, services.option_variants, services.deadline, services.public, services.sort_order, services.braintree_plan_id, services.group_quantities, services.folder_id, services.metadata, services.hoth_product_key, services.hoth_package_name, services.created_at, services.updated_at, services.provider_id, services.provider_service_id, services.deleted_at, orders, invoice_items, addons, parent_services, folder, reseller_provider, tasks, workflowSteps, intakeForm, onboardingForms, addon_orders, getFieldsAttribute, employees, audits, morphMetadata, media, logs.
service_idNoService id. Required for "show" actions.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The description is consistent with the readOnlyHint and destructiveHint annotations; it only describes read operations and does not imply side effects. It does not add extra behavioral details like auth or rate limits, but the annotations already cover the core read-only nature.

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

Conciseness5/5

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

The description is one concise sentence that enumerates the valid actions and highlights the key list capability. It avoids unnecessary prose and front-loads the main purpose.

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?

Given the lack of an output schema, the description covers the main operations and the list capabilities. It could be slightly more explicit about the differing outputs of 'show' vs 'get_task_templates', but the action enum and parameter descriptions fill most gaps.

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?

The schema provides detailed descriptions for most parameters, including the action enum, filter example, and sortable fields. The description adds little beyond those schema details, and the phrase 'Purity filter object' appears to be a typo that could slightly confuse, though the example mitigates it.

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 description clearly states the three read actions ('list', 'show', 'get_task_templates') and the resource type (services). It is readily distinguishable from the sibling service-write tool.

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?

The description notes that list supports filtering, sorting, and pagination, but it does not explicitly say when to use this read tool versus the sibling service-write alternative. Action-specific requirements are left to the parameter descriptions rather than stated as usage guidance.

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