Skip to main content
Glama

Jobiba Hiring: Post Jobs, Screen Applicants & Source Talent

See Jobiba plans & pricing

get_membership_plans
Read-onlyIdempotent

Public plan and pricing information. Jobiba has no paid candidate plan (candidate tools are free); employer plans (Free, Starter, Growth, Enterprise) list prices, limits and features. No payment is taken by this tool.

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_membership_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds genuine value beyond that: it states no payment is transacted and no candidate plan is paid, which prevents an agent from treating this as a billing action. It does not say anything about freshness or caching of pricing data.

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?

Three short sentences, front-loaded with the resource, then the scope breakdown, then the non-billing disclaimer. No filler, though the parenthetical aside about free candidate tools slightly interrupts the flow of the plan enumeration.

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 zero-argument, read-only information tool with no output schema, the description covers what data is returned (prices, limits, features per tier) and what it does not do (take payment). The only remaining gap is that return structure/format is unstated, which is a minor omission given no output schema exists to describe it.

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?

The tool takes zero parameters, so there is no schema meaning to supplement and the baseline of 4 applies. The description does not need to explain inputs and correctly spends no words on them.

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 — public plan and pricing information — and enumerates the employer tiers (Free, Starter, Growth, Enterprise) along with what each lists (prices, limits, features). It also clarifies the candidate side is free, which sharpens the scope. It does not explicitly contrast itself with get_my_plan or start_plan_upgrade, so sibling differentiation is left implicit.

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: 'No payment is taken by this tool' hints that an actual upgrade/payment path lives elsewhere (likely start_plan_upgrade or get_my_plan), but no alternative is named and no when-to-use condition is stated. An agent can infer this is the catalog-lookup tool, but must guess at the routing.

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.