Skip to main content
Glama

create_filter

Create a company filter by specifying display name, section, default status, and rules to organize records in subscription billing.

Instructions

Create a company filter. POST /companies/filters. Required: displayName, section, isDefault, rules (array of { operatorId, attributeId, settingValues }). Optional per rule: operatorDisplayName. Section: billRuns, companyInbox, companyInvoices, companyLogs, companyNotifications, companyUpcomingSchedule, creditNotes, customers, ...

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
displayNameYesDisplay name (required)
sectionYesSection (required). One of: subscriptions, invoices, customers, products, orders, etc.
isDefaultYesSet as default filter (required)
rulesYesRules array (required). Each: operatorId (number), attributeId (number), settingValues (array of { value }), optional operatorDisplayName
Behavior2/5

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

No annotations exist; description only mentions HTTP method and required/optional fields, omitting side effects, permissions, idempotency, or limits.

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?

Description is fairly concise with purpose first, though the section list is lengthy but still front-loaded.

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?

Lacks return value or error information; adequate for a creation tool given schema detail but missing output context.

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 descriptions cover 100% of parameters; description adds required/optional distinction, rule structure example, and section enumeration, providing meaningful extra context.

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?

Clearly states 'Create a company filter', a specific verb and resource, differentiating from siblings like list_filters and remove_filter.

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?

Implies usage for creating filters but provides no explicit guidance on when to use versus alternatives or exclusion criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rhinosaas/rebillia-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server