A
license-
qualityB
maintenanceSearch live startup.jobs listings with filters for role, location, and employment type, plus get job details, company profiles, hiring trends, and salary benchmarks.
MIT
Pawlisty Pet Listings
by com.pawlisty
Server Details
Search live Pawlisty pet listings by species, breed, location, and price.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.2/5.0
Tool DescriptionsA
Average 4/5 across 4 of 4 tools scored.
Server CoherenceA
Disambiguation5/5
Each tool has a clear, distinct purpose: browsing breeds, getting buyer safety info, retrieving listing details, and searching listings. No overlap or confusion possible.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case (browse_breeds, get_buying_guide, get_pet_listing, search_pet_listings).
Tool Count5/5
With 4 tools covering breed info, safety guidance, listing details, and search, the set is well-scoped for a buyer-focused pet listing service.
Completeness4/5
Covers core buyer workflows (search, detail, breed research, safety). Minor gap: no tool to list all available species or filter by more attributes, but not a critical omission.
Available Tools
4 toolsbrowse_breedsAInspect
List pet breeds Pawlisty covers, with links to breed guides and current availability. Use when comparing breeds or researching before buying. Returns a breed id usable in search_pet_listings.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | No | Breed name fragment. | |
| species | No |
Tool Definition Quality
A4.1/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses that the tool lists breeds with links and availability, and returns an ID, implying read-only behavior. No hidden side effects, but lacks details on authentication or rate limits.
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?
Three concise sentences, front-loaded with main action, then usage guidance, then return value. No wasted words.
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?
Tool is simple (list breeds) with 3 optional params and no output schema. Description covers purpose, usage, and return value linkage to sibling tool. Lacks details on pagination/limit behavior and precise semantics of species enum.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 33% (only 'query' has a description). The description text does not explain the other two parameters (limit, species), leaving their semantics unclear. The tool description adds minimal value beyond schema.
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 tool lists pet breeds, with links to guides and availability, and distinguishes it from siblings like search_pet_listings by returning a breed ID usable in that tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides explicit when-to-use advice ('when comparing breeds or researching before buying') and hints at workflow (breed id usable in search_pet_listings), but does not mention when not to use or alternative tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_buying_guideAInspect
Return Pawlisty buyer-safety guidance (avoiding pet scams, FAQ on buying/adopting safely). Use for any "how do I safely buy or adopt a pet" or "is this listing a scam" question. Returns a summary and a link to the full guide on pawlisty.com.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| topic | No | Which guide. Omit to return all buyer guides. |
Tool Definition Quality
A3.8/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description only mentions return type (summary and link) without disclosing any side effects, permissions, or rate limits. For a read-only information tool, basic transparency is present but minimal.
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?
Two sentences, front-loaded with purpose and usage. Every sentence adds value with no extraneous words.
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?
Tool is simple with one parameter; description covers return values and intended use. Sibling tools are distinct, providing sufficient context. Minor lack: no mention of expected response format, but acceptable for a simple guide retrieval.
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 coverage is 100% and includes a clear description for the topic parameter. The description reiterates the 'omit to return all' behavior already present in the schema, adding no new semantic value beyond output information.
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?
Description clearly states it returns buyer-safety guidance for pet scams and safe adoption, distinct from sibling tools that deal with breed browsing and listings. Verb and resource are specific.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states use case for safety questions ('how do I safely buy/adopt' or 'is this a scam'), providing clear context. Does not explicitly state when not to use, but sibling tools imply alternative uses.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_pet_listingAInspect
Get full details for one Pawlisty listing by id. Use after search_pet_listings when the user wants more on a specific pet. To contact the seller the user must visit the listing page.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Listing id. |
Tool Definition Quality
A4.2/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It implies a read operation but does not explicitly state read-only, nor mention authentication requirements or whether the response includes all fields. Adequate but could be more precise.
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?
Two concise sentences: first states purpose and usage context, second adds a practical limitation. No unnecessary words.
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 simple retrieval tool with one parameter and no output schema, the description covers what it does, when to use, and a key limitation. Could hint at the structure of 'full details' but is sufficient as is.
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?
Only one parameter with schema description 'Listing id.' Description adds little beyond the schema (just 'by id'). With 100% schema coverage, baseline 3 is appropriate.
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 the action ('Get full details'), the resource ('Pawlisty listing'), and the identifier ('by id'). Distinguishes from sibling 'search_pet_listings' which searches instead of retrieving a single record.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly tells when to use this tool ('after search_pet_listings when the user wants more on a specific pet') and what not to expect ('To contact the seller the user must visit the listing page').
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_pet_listingsAInspect
Search live pet listings for sale or adoption on Pawlisty. Use whenever a user wants to buy or adopt a pet or asks what is available, filtered by species, breed, location, price, or care attributes. Returns current listings with links to pawlisty.com.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| age | No | newborn 0-8wk, young 2-6mo, adolescent 6-12mo, adult 1-7yr, senior 7+yr. | |
| size | No | ||
| sort | No | relevance | |
| breed | No | Breed name; resolved to a breed id. Use browse_breeds to disambiguate. | |
| limit | No | ||
| query | No | Free-text keywords. | |
| gender | No | ||
| city_id | No | Exact city id if known. | |
| desexed | No | Neutered or spayed. | |
| species | No | ||
| location | No | City or place name. | |
| good_with | No | ||
| price_max | No | ||
| price_min | No | ||
| vaccinated | No | ||
| distance_km | No | ||
| country_code | No | ISO 3166-1 alpha-2 (e.g. US, GB). Defaults to the site default. | |
| listing_type | No | for_sale | |
| verified_only | No | Only photo-verified listings. |
Tool Definition Quality
A3.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must cover behavioral traits. It implies a read-only search operation but does not explicitly state it's non-destructive, mention authentication needs, rate limits, or return behavior (e.g., pagination). Adequate but not rich.
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 three sentences, front-loaded with the main purpose, and every sentence adds value. No fluff.
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?
Given the tool's complexity (19 parameters, no output schema, no annotations), the description covers purpose, usage, and general output. However, it lacks details on result structure, error handling, or sorting/pagination behavior, leaving gaps for an agent.
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 only 42%. The description lists filterable attributes (species, breed, location, price, care) but does not detail each parameter. It adds some context beyond the schema but does not fully compensate for the low coverage.
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 'Search live pet listings for sale or adoption on Pawlisty' and lists common filter attributes. It differentiates from sibling tools (browse_breeds, get_buying_guide, get_pet_listing) by focusing on search/filtering.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit when-to-use context ('Use whenever a user wants to buy or adopt a pet or asks what is available'). It does not state when NOT to use or mention alternatives explicitly, but the purpose is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables searching Austria's largest classifieds marketplace (willhaben.at) for real estate, cars, jobs, and second-hand items via natural-language queries and structured filters, with full listing details.7161MIT
JobsPipe MCP Serverofficial
Flicense-qualityBmaintenanceEnables searching live, normalized job postings from 30+ ATS feeds and job boards, with tools for job search, source listing, pricing plans, and Upwork jobs.- -license-quality-maintenanceEnables searching and filtering real estate properties in France through the Melo API. Supports comprehensive property searches with filters for price, surface area, location, and property type for both sales and rentals.